pysec-2020-156
Vulnerability from pysec
Published
2020-01-29 15:15
Modified
2020-02-03 16:36
Details

flaskparser.py in Webargs 5.x through 5.5.2 doesn't check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.

Impacted products
Name purl
webargs pkg:pypi/webargs



{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "webargs",
        "purl": "pkg:pypi/webargs"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.0.0"
            },
            {
              "fixed": "5.5.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "5.0.0",
        "5.1.0",
        "5.1.1",
        "5.1.1.post0",
        "5.1.2",
        "5.1.3",
        "5.2.0",
        "5.3.0",
        "5.3.1",
        "5.3.2",
        "5.4.0",
        "5.5.0",
        "5.5.1",
        "5.5.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2020-7965",
    "GHSA-fjq3-5pxw-4wj4"
  ],
  "details": "flaskparser.py in Webargs 5.x through 5.5.2 doesn\u0027t check that the Content-Type header is application/json when receiving JSON input. If the request body is valid JSON, it will accept it even if the content type is application/x-www-form-urlencoded. This allows for JSON POST requests to be made across domains, leading to CSRF.",
  "id": "PYSEC-2020-156",
  "modified": "2020-02-03T16:36:00Z",
  "published": "2020-01-29T15:15:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://webargs.readthedocs.io/en/latest/changelog.html"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-fjq3-5pxw-4wj4"
    }
  ]
}


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…