What is CVE-2023-6180?

CVE-2023-6180 is a medium-severity uncontrolled resource consumption vulnerability in tokio-boring (rust), affecting versions = 4.0.0. It is fixed in 4.1.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2023-6180?

CVE-2023-6180 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of tokio-boring are affected by CVE-2023-6180?

tokio-boring (rust) versions = 4.0.0 is affected.

Is there a fix for CVE-2023-6180?

Yes. CVE-2023-6180 is fixed in 4.1.0. Upgrade to this version or later.

Is CVE-2023-6180 exploitable, and should I be worried?

Whether CVE-2023-6180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-6180 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-6180?

Upgrade tokio-boring to 4.1.0 or later.

CVE-2023-6180 in tokio-boring

Summary

tokio-boring vulnerable to resource exhaustion via memory leak

References

CVE-2023-6180 at cve.org

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.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2023-6180 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.1.0); upgrading removes the vulnerable code path.

Affected versions

tokio-boring (= 4.0.0)

Security releases

tokio-boring → 4.1.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2023-6180? CVE-2023-6180 is a medium-severity uncontrolled resource consumption vulnerability in tokio-boring (rust), affecting versions = 4.0.0. It is fixed in 4.1.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2023-6180? CVE-2023-6180 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of tokio-boring are affected by CVE-2023-6180? tokio-boring (rust) versions = 4.0.0 is affected.
Is there a fix for CVE-2023-6180? Yes. CVE-2023-6180 is fixed in 4.1.0. Upgrade to this version or later.
Is CVE-2023-6180 exploitable, and should I be worried? Whether CVE-2023-6180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-6180 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-6180? Upgrade tokio-boring to 4.1.0 or later.