Description
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.
Published: 2020-01-29
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

No analysis available yet.

Remediation

No remediation available yet.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
EUVD EUVD EUVD-2020-0240 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.
Github GHSA Github GHSA GHSA-fjq3-5pxw-4wj4 Cross-Site Request Forgery in Webargs
History

No history.

Subscriptions

Webargs Project Webargs
cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-04T09:48:25.379Z

Reserved: 2020-01-24T00:00:00.000Z

Link: CVE-2020-7965

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-01-29T15:15:11.070

Modified: 2024-11-21T05:38:06.243

Link: CVE-2020-7965

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses