First published: Tue Dec 05 2023(Updated: )
### 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)
Credit: cna@cloudflare.com cna@cloudflare.com
Affected Software | Affected Version | How to fix |
---|---|---|
rust/tokio-boring | =4.0.0 | 4.1.0 |
Cloudflare Boring | =4.0.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The impact of CVE-2023-6180 is excessive resource consumption and potential DoS by resource exhaustion.
The severity of CVE-2023-6180 is medium with a CVSS score of 5.3.
To fix CVE-2023-6180, update to version 4.1.0 of the tokio-boring library.
The CWE of CVE-2023-6180 is 400, 404, 401.
You can find more information about CVE-2023-6180 in the following references: [GitHub Advisory](https://github.com/cloudflare/boring/security/advisories/GHSA-pjrj-h4fg-6gm4), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-6180), [GitHub Commit](https://github.com/cloudflare/boring/commit/a32783374f2682e6949fdb713910b1b9f103d3ed).