Skip to content

Requests `Session` object does not verify requests after making first request with verify=False

Moderate severity GitHub Reviewed Published May 20, 2024 in psf/requests • Updated Jun 10, 2024

Package

pip requests (pip)

Affected versions

< 2.32.0

Patched versions

2.32.0

Description

When making requests through a Requests Session, if the first request is made with verify=False to disable cert verification, all subsequent requests to the same origin will continue to ignore cert verification regardless of changes to the value of verify. This behavior will continue for the lifecycle of the connection in the connection pool.

Remediation

Any of these options can be used to remediate the current issue, we highly recommend upgrading as the preferred mitigation.

  • Upgrade to requests>=2.32.0.
  • For requests<2.32.0, avoid setting verify=False for the first request to a host while using a Requests Session.
  • For requests<2.32.0, call close() on Session objects to clear existing connections if verify=False is used.

Related Links

References

@nateprewitt nateprewitt published to psf/requests May 20, 2024
Published to the GitHub Advisory Database May 20, 2024
Reviewed May 20, 2024
Published by the National Vulnerability Database May 20, 2024
Last updated Jun 10, 2024

Severity

Moderate

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
Local
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-35195

GHSA ID

GHSA-9wx4-h78v-vm56

Source code

Credits

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