Skip to content

← Public intelligence

PyPI package

webargs

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7PyPIAmendedPublished

    Cross-Site Request Forgery in Webargs

    CVE-2020-7965 · GHSA-fjq3-5pxw-4wj4

    Affected
    • PyPI webargs >= 5.0.0, < 5.5.3; >= 6.0.0b1, < 6.0.0b4
    Fixed in
    6.0.0b45.5.3· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 6.0.0b4 (pre-release) or 5.5.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.2PyPIAmendedPublished

    Webargs mishandles concurrent JSON parsing

    CVE-2019-9710 · GHSA-8554-jxcw-454q

    Affected
    • PyPI webargs < 5.1.3
    Fixed in
    5.1.3· Vendor fix available
    Issue
    An issue was discovered in webargs before 5.1.3, as used with marshmallow and other products. JSON parsing uses a short-lived cache to store the parsed JSON body. This cache is not thread-safe, meaning that incorrect JSON payloads could have been parsed for concurrent requests.

    Recommended action: Upgrade to 5.1.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →