pysec-2022-256
Vulnerability from pysec
Published
2022-08-26 16:15
Modified
2022-08-31 20:34
Details

The Deluge Web-UI is vulnerable to XSS through a crafted torrent file. The the data from torrent files is not properly sanitised as it's interpreted directly as HTML. Someone who supplies the user with a malicious torrent file can execute arbitrary Javascript code in the context of the user's browser session.

Impacted products
Name purl
deluge pkg:pypi/deluge



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "deluge",
            purl: "pkg:pypi/deluge",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "2.1.0",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.0.0",
            "2.0.0b2.dev346",
            "2.0.0b2.dev347",
            "2.0.0b2.dev355",
            "2.0.2",
            "2.0.3",
            "2.0.4",
            "2.0.5",
         ],
      },
   ],
   aliases: [
      "CVE-2021-3427",
      "GHSA-5c8p-qhch-qhx6",
   ],
   details: "The Deluge Web-UI is vulnerable to XSS through a crafted torrent file. The the data from torrent files is not properly sanitised as it's interpreted directly as HTML. Someone who supplies the user with a malicious torrent file can execute arbitrary Javascript code in the context of the user's browser session.",
   id: "PYSEC-2022-256",
   modified: "2022-08-31T20:34:06.230496Z",
   published: "2022-08-26T16:15:00Z",
   references: [
      {
         type: "WEB",
         url: "https://groups.google.com/g/deluge-dev/c/e5zh7wT0rEg",
      },
      {
         type: "WEB",
         url: "https://dev.deluge-torrent.org/ticket/3459",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-5c8p-qhch-qhx6",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.