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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
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 |
GHSA-fjq3-5pxw-4wj4 | Cross-Site Request Forgery in Webargs |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://webargs.readthedocs.io/en/latest/changelog.html |
|
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T09:48:25.379Z
Reserved: 2020-01-24T00:00:00
Link: CVE-2020-7965
No data.
Status : Modified
Published: 2020-01-29T15:15:11.070
Modified: 2024-11-21T05:38:06.243
Link: CVE-2020-7965
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA