Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2023-6180

MEDIUM
Published 2023-12-05T15:02:40.007Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2023-6180. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
5.3
/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14
0.001
probability
of exploitation in the wild

There is a 0.1% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25
Exploit Probability
Percentile: 0.230
Higher than 23.0% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
NONE
Integrity
NONE
Availability
LOW

Description

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

Cloudflare

tokio-boring

Affected Versions:

4.0.0

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

tokio-boring vulnerable to resource exhaustion via memory leak

GHSA-pjrj-h4fg-6gm4

Advisory Details

### 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](https://www.cve.org/CVERecord?id=CVE-2023-6180)

Affected Packages

crates.io tokio-boring
ECOSYSTEM: ≥4.0.0 <4.1.0

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

WEB https://github.com/cloudflare/boring/security/advisories/GHSA-pjrj-h4fg-6gm4
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2023-6180
WEB https://github.com/cloudflare/boring/commit/a32783374f2682e6949fdb713910b1b9f103d3ed
PACKAGE https://github.com/cloudflare/boring

Advisory provided by GitHub Security Advisory Database. Published: December 5, 2023, Modified: December 5, 2023

References

https://github.com/cloudflare/boring/security/advisories/GHSA-pjrj-h4fg-6gm4
Published: 2023-12-05T15:02:40.007Z
Last Modified: 2024-08-02T08:21:17.825Z
Copied to clipboard!