Skip to content

Duplicate Advisory: Integer Overflow in HeaderMap::reserve() can cause Denial of Service

High severity GitHub Reviewed Published Jun 16, 2022 to the GitHub Advisory Database • Updated Feb 21, 2024
Withdrawn This advisory was withdrawn on Feb 21, 2024

Package

cargo http (Rust)

Affected versions

< 0.1.20

Patched versions

0.1.20

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-x7vr-c387-8w57. This link is maintained to preserve external references.

Original Description

HeaderMap::reserve() used usize::next_power_of_two() to calculate the increased capacity. However, next_power_of_two() silently overflows to 0 if given a sufficiently large number in release mode.

If the map was not empty when the overflow happens, the library will invoke self.grow(0) and start infinite probing. This allows an attacker who controls the argument to reserve() to cause a potential denial of service (DoS).

The flaw was corrected in 0.1.20 release of http crate.

References

Published to the GitHub Advisory Database Jun 16, 2022
Reviewed Jun 16, 2022
Withdrawn Feb 21, 2024
Last updated Feb 21, 2024

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.241%
(63rd percentile)

Weaknesses

CVE ID

CVE-2019-25008

GHSA ID

GHSA-xvc9-xwgj-4cq9

Source code

Credits

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