Skip to content

Webargs mishandles concurrent JSON parsing

High severity GitHub Reviewed Published Mar 12, 2019 to the GitHub Advisory Database • Updated Aug 30, 2023

Package

pip webargs (pip)

Affected versions

< 5.1.3

Patched versions

5.1.3

Description

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.

References

Published to the GitHub Advisory Database Mar 12, 2019
Reviewed Jun 16, 2020
Last updated Aug 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.246%
(65th percentile)

Weaknesses

CVE ID

CVE-2019-9710

GHSA ID

GHSA-8554-jxcw-454q

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.