Skip to content

tokio-boring vulnerable to resource exhaustion via memory leak

Moderate severity GitHub Reviewed Published Dec 5, 2023 in cloudflare/boring

Package

cargo tokio-boring (Rust)

Affected versions

= 4.0.0

Patched versions

4.1.0

Description

Impact

The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The set_ex_data function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.

Patches

The issue is fixed in version 4.1.0 of tokio-boring.

References

CVE-2023-6180 at cve.org

References

@mskowroncf mskowroncf published to cloudflare/boring Dec 5, 2023
Published by the National Vulnerability Database Dec 5, 2023
Published to the GitHub Advisory Database Dec 5, 2023
Reviewed Dec 5, 2023

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

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:L

EPSS score

0.046%
(18th percentile)

Weaknesses

CVE ID

CVE-2023-6180

GHSA ID

GHSA-pjrj-h4fg-6gm4

Source code

Credits

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