pysec-2019-112
Vulnerability from pysec
Published
2019-12-26 23:15
Modified
2020-01-02 14:27
Details

In Archery before 1.3, inserting an XSS payload into a project name (either by creating a new project or editing an existing one) will result in stored XSS on the vulnerability-scan scheduling page.

Impacted products
Name purl
pyarchery pkg:pypi/pyarchery
Aliases



{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "pyarchery",
        "purl": "pkg:pypi/pyarchery"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.3.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1",
        "0.2",
        "0.3",
        "1.0",
        "1.1.0",
        "1.2.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2019-20008"
  ],
  "details": "In Archery before 1.3, inserting an XSS payload into a project name (either by creating a new project or editing an existing one) will result in stored XSS on the vulnerability-scan scheduling page.",
  "id": "PYSEC-2019-112",
  "modified": "2020-01-02T14:27:00Z",
  "published": "2019-12-26T23:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://github.com/archerysec/archerysec/issues/338"
    },
    {
      "type": "WEB",
      "url": "https://github.com/archerysec/archerysec/compare/archerysec-v1.2...v1.3"
    },
    {
      "type": "WEB",
      "url": "https://github.com/archerysec/archerysec/releases/tag/v1.3"
    }
  ]
}


Log in or create an account to share your comment.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.


Loading…

Loading…