{"id":"CVE-2023-6180","aliases":["EUVD-2023-3262","GHSA-pjrj-h4fg-6gm4"],"status":"published","title":"Resource exhaustion via memory leak in tokio-boring","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.","severity":{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00619,"percentile":0.49943,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400","CWE-401","CWE-404"],"published":"2023-12-05T15:02:40Z","modified":"2026-10-28T02:30:39Z","fixes":[{"ecosystem":"crates.io","package":"tokio-boring","fixed_in":["4.1.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"tokio-boring","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"last_affected":"4.0.0"},{"fixed":"4.1.0"}]}],"versions":["4.0.0"]},{"source":"osv","ecosystem":"crates.io","package":"tokio-boring","ranges":[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"4.1.0"}]}],"versions":["4.0.0"]}],"products":[{"vendor":"cloudflare","product":"boring"},{"vendor":"cloudflare","product":"tokio-boring"}],"references":[{"url":"https://github.com/cloudflare/boring/security/advisories/GHSA-pjrj-h4fg-6gm4","tags":["x_transferred","Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6180","tags":["advisory"]},{"url":"https://github.com/cloudflare/boring/commit/a32783374f2682e6949fdb713910b1b9f103d3ed","tags":["web"]},{"url":"https://github.com/advisories/GHSA-pjrj-h4fg-6gm4"},{"url":"https://github.com/cloudflare/boring/tree/master/tokio-boring","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/6xxx/CVE-2023-6180.json","tags":["advisory"]},{"url":"https://github.com/cloudflare/boring","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2023-6180","title":"Resource exhaustion via memory leak in tokio-boring","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.\n","status":"published","published":"2023-12-05T15:02:40.007Z","modified":"2024-08-02T08:21:17.825Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"cna"}],"cwes":["CWE-400","CWE-404"],"updated_at":"2026-11-02T14:35:25.469654Z"}],"euvd":[{"id":"EUVD-2023-3262","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.\n","status":"published","published":"2023-12-05T15:02:40Z","modified":"2024-08-02T08:21:17Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"updated_at":"2026-11-03T03:50:11.066935Z"}],"ghsa":[{"id":"GHSA-pjrj-h4fg-6gm4","title":"tokio-boring vulnerable to resource exhaustion via memory leak","description":"### Impact\nThe 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.\n\n### Patches\nThe issue is fixed in version 4.1.0 of tokio-boring.\n\n### References\n[CVE-2023-6180 at cve.org](https://www.cve.org/CVERecord?id=CVE-2023-6180)\n","status":"published","published":"2023-12-05T23:42:49Z","modified":"2023-12-05T23:42:49Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"cwes":["CWE-400","CWE-401","CWE-404"],"updated_at":"2026-11-02T14:37:23.843848Z"}],"nvd":[{"id":"CVE-2023-6180","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.\n","status":"published","published":"2023-12-05T15:15:08.703Z","modified":"2026-06-17T06:50:15.297Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"secondary"},{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium","assessor":"primary"}],"cwes":["CWE-400","CWE-404","CWE-401"],"updated_at":"2026-11-02T14:08:54.010507Z"}],"osv":[{"id":"CVE-2023-6180","title":"Resource exhaustion via memory leak in tokio-boring","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.\n","status":"published","published":"2023-12-05T15:02:40.007Z","modified":"2026-10-28T02:30:39.021437366Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"cwes":["CWE-400","CWE-404"],"updated_at":"2026-11-02T15:44:36.851042Z"},{"id":"GHSA-pjrj-h4fg-6gm4","title":"tokio-boring vulnerable to resource exhaustion via memory leak","description":"### Impact\nThe 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.\n\n### Patches\nThe issue is fixed in version 4.1.0 of tokio-boring.\n\n### References\n[CVE-2023-6180 at cve.org](https://www.cve.org/CVERecord?id=CVE-2023-6180)\n","status":"published","published":"2023-12-05T23:42:49Z","modified":"2026-07-08T06:29:08.895269677Z","cvss":[{"version":"3.1","score":5.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","level":"medium"}],"cwes":["CWE-400","CWE-401","CWE-404"],"updated_at":"2026-11-02T15:46:53.244788Z"}]}}