Read the docs
TI-2023-05677 Aliases CVE-2023-6180GHSA-pjrj-h4fg-6gm4

Resource exhaustion via memory leak in tokio-boring

Priority LOW 25CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.

Summary

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.

Why it matters now

EPSS 0.00619 49th percentileScored 2026-11-07
Fix Fixed tokio-boring (crates.io): 4.1.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Cloudflaretokio-boring4.0.0 – 4.1.0—No fix listedCNA
—tokio-boring (crates.io)4.0.0 to before 4.1.04.1.0Patch availableGHSA-pjrj-h4fg-6gm4
  • tokio-boring VendorCloudflare Affected 4.0.0 – 4.1.0 Fixed in — No fix listed CNA
  • tokio-boring (crates.io) Vendor— Affected 4.0.0 to before 4.1.0 Fixed in 4.1.0 Patch available GHSA-pjrj-h4fg-6gm4

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:cloudflare:boring:4.0.0:*:*:*:*:rust:*:*4.0.0VulnerableCloudflare
  • cpe:2.3:a:cloudflare:boring:4.0.0:*:*:*:*:rust:*:* Versions 4.0.0 Vulnerable ·Cloudflare

Remediation

  • Fix · GHSA-pjrj-h4fg-6gm4 tokio-boring (crates.io) Fixed in 4.1.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2023-6180
  2. 2026-10-03 Alias added: GHSA-pjrj-h4fg-6gm4

References

Sources