GHSA-652x-xj99-gmcc CVE-2014-1830 PYSEC-2014-14

Exposure of Sensitive Information to an Unauthorized Actor in Requests

Medium PyPI

Severity: 0.0 / 10; Medium · CVSS 4.0
Exploit chance (EPSS): 2.04%; Chance of exploitation in the next 30 days. Higher than 81.10% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix: 2.3.0; Upgrade requests to this version or later

Description

Requests (aka python-requests) before 2.3.0 allows remote servers to obtain sensitive information by reading the Proxy-Authorization header in a redirected request.

Affected versions

PyPI

Package	Vulnerable	Fixed in
requests	`< 2.3.0`	`2.3.0`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

requests PyPI → `2.3.0`

pip

pip install --upgrade "requests>=2.3.0"

poetry

poetry add "requests>=2.3.0"

uv

uv add "requests>=2.3.0"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: None
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): Low
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it

Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

github.com/psf/requests

Timeline

Oct 15, 2014 Published
Oct 21, 2024 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-gc5v-m9x4-r6x2 Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function	Medium	Also affects requests
GHSA-9hjg-9r4m-mvj7 Requests vulnerable to .netrc credentials leak via malicious URLs	Medium	Also affects requests
GHSA-9wx4-h78v-vm56 Requests `Session` object does not verify requests after making first request with verify=False	Medium	Also affects requests
GHSA-j8r2-6x86-q33q Unintended leak of Proxy-Authorization header in requests	Medium	Also affects requests
GHSA-x84v-xcm2-53pg Insufficiently Protected Credentials in Requests	High	Also affects requests
GHSA-pg2w-x9wp-vw92 Python Requests Session Fixation	Medium	Also affects requests
GHSA-cfj3-7x9c-4p3h Exposure of Sensitive Information to an Unauthorized Actor in Requests	Medium	Also affects requests
GHSA-j7qq-vr8c-xvw3 MLflow CrewAI autologging records LLM provider API keys in logged trace spans	Medium	Same weakness, CWE-200

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor