What is GHSA-Q95X-7G78-RCCV?

GHSA-Q95X-7G78-RCCV is a medium-severity use after free vulnerability in oneringbuf (rust), affecting versions < 0.8.0. It is fixed in 0.8.0. Memory is accessed after it has been freed, leading to undefined behavior in native code.

Which versions of oneringbuf are affected by GHSA-Q95X-7G78-RCCV?

oneringbuf (rust) versions < 0.8.0 is affected.

Is there a fix for GHSA-Q95X-7G78-RCCV?

Yes. GHSA-Q95X-7G78-RCCV is fixed in 0.8.0. Upgrade to this version or later.

Is GHSA-Q95X-7G78-RCCV exploitable, and should I be worried?

Whether GHSA-Q95X-7G78-RCCV 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 GHSA-Q95X-7G78-RCCV 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.

GHSA-Q95X-7G78-RCCV in oneringbuf

Q: Which versions of oneringbuf are affected by GHSA-Q95X-7G78-RCCV?

oneringbuf (rust) versions < 0.8.0 is affected.

Q: Is there a fix for GHSA-Q95X-7G78-RCCV?

Yes. GHSA-Q95X-7G78-RCCV is fixed in 0.8.0. Upgrade to this version or later.

Q: Is GHSA-Q95X-7G78-RCCV exploitable, and should I be worried?

Whether GHSA-Q95X-7G78-RCCV 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.

Q: What actually determines whether GHSA-Q95X-7G78-RCCV 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.

Q: How do I fix GHSA-Q95X-7G78-RCCV?

Upgrade oneringbuf to 0.8.0 or later.

Summary

OneRingBuf has a Use After Free Vulnerability

Affected versions of oneringbuf exposed the obsolete IntoRef::into_ref method through the public IntoRef trait. For heap-backed ring buffers, this method returned a DroppableRef handle.

DroppableRef stored an owning raw pointer created from Box::into_raw. Its Clone implementation copied this raw pointer without incrementing the internal alive_iters counter. Internally, this clone pattern appears to rely on a fixed number of handles being created to match the initial alive_iters value. However, exposing DroppableRef through the public IntoRef::TargetRef associated type allows safe external code to create additional clones beyond that fixed count, breaking the lifetime protocol. Drop later dereferenced the pointer and could free the backing allocation with Box::from_raw.

Safe code could call IntoRef::into_ref to obtain a DroppableRef and then clone it. Each clone pointed to the same allocation, but the internal alive_iters counter was not increased. As a result, one clone could free the allocation while another clone still existed. Dropping the remaining clone then accessed freed memory, causing a heap-use-after-free.

The issue was fixed in version 0.8.0 by removing the obsolete into_ref method.

Trigger

use oneringbuf::{IntoRef, LocalHeapRB};

fn main() {
    let rb = LocalHeapRB::<usize>::from(vec![1, 2, 3]);

    let r = <LocalHeapRB<usize> as IntoRef>::into_ref(rb);
    let r2 = r.clone();
    let r3 = r.clone();

    drop(r);
    drop(r2);
    drop(r3); // AddressSanitizer: heap-use-after-free
}

Impact

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

Affected versions

oneringbuf (< 0.8.0)

Security releases

oneringbuf → 0.8.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

Upgrade oneringbuf to 0.8.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-Q95X-7G78-RCCV? GHSA-Q95X-7G78-RCCV is a medium-severity use after free vulnerability in oneringbuf (rust), affecting versions < 0.8.0. It is fixed in 0.8.0. Memory is accessed after it has been freed, leading to undefined behavior in native code.
Which versions of oneringbuf are affected by GHSA-Q95X-7G78-RCCV? oneringbuf (rust) versions < 0.8.0 is affected.
Is there a fix for GHSA-Q95X-7G78-RCCV? Yes. GHSA-Q95X-7G78-RCCV is fixed in 0.8.0. Upgrade to this version or later.
Is GHSA-Q95X-7G78-RCCV exploitable, and should I be worried? Whether GHSA-Q95X-7G78-RCCV 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 GHSA-Q95X-7G78-RCCV 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 GHSA-Q95X-7G78-RCCV? Upgrade oneringbuf to 0.8.0 or later.