What is CVE-2024-8375?

CVE-2024-8375 is a medium-severity use after free vulnerability in dm-reverb (pip), affecting versions <= 0.14.0. No fixed version is listed yet. Memory is accessed after it has been freed, leading to undefined behavior in native code.

How severe is CVE-2024-8375?

CVE-2024-8375 has a CVSS score of 6.1 (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 packages are affected by CVE-2024-8375?

dm-reverb (pip) versions <= 0.14.0; dm-reverb-nightly (pip) versions <= 0.15.0.dev20240214.

Is there a fix for CVE-2024-8375?

No fixed version is listed for CVE-2024-8375 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2024-8375 exploitable, and should I be worried?

Whether CVE-2024-8375 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-2024-8375 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.

CVE-2024-8375 in dm-reverb

Q: How severe is CVE-2024-8375?

CVE-2024-8375 has a CVSS score of 6.1 (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.

Q: Which packages are affected by CVE-2024-8375?

dm-reverb (pip) versions <= 0.14.0; dm-reverb-nightly (pip) versions <= 0.15.0.dev20240214.

Q: Is there a fix for CVE-2024-8375?

No fixed version is listed for CVE-2024-8375 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2024-8375 exploitable, and should I be worried?

Whether CVE-2024-8375 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 CVE-2024-8375 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 CVE-2024-8375?

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use memory-safe data structures and address sanitizers during testing.

Summary

Reverb use after free vulnerability

There exists a use after free vulnerability in Reverb. Reverb supports the VARIANT datatype, which is supposed to represent an arbitrary object in C++. When a tensor proto of type VARIANT is unpacked, memory is first allocated to store the entire tensor, and a ctor is called on each instance. Afterwards, Reverb copies the content in tensor_content to the previously mentioned pre-allocated memory, which results in the bytes in tensor_content overwriting the vtable pointers of all the objects which were previously allocated. Reverb exposes 2 relevant gRPC endpoints: InsertStream and SampleStream. The attacker can insert this stream into the server’s database, then when the client next calls SampleStream they will unpack the tensor into RAM, and when any method on that object is called (including its destructor) the attacker gains control of the Program Counter. We recommend upgrading past git commit https://github.com/google-deepmind/reverb/commit/6a0dcf4c9e842b7f999912f792aaa6f6bd261a25

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.

CVE-2024-8375 has a CVSS score of 6.1 (Medium). The vector is requires local access, low privileges required, and user interaction required. 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. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

dm-reverb (<= 0.14.0) dm-reverb-nightly (<= 0.15.0.dev20240214)

Security releases

Not available

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

No fixed version is listed for CVE-2024-8375 yet.

In the interim: Keep the dependency up to date. In native-code projects, use memory-safe data structures and address sanitizers during testing.

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

Frequently Asked Questions

What is CVE-2024-8375? CVE-2024-8375 is a medium-severity use after free vulnerability in dm-reverb (pip), affecting versions <= 0.14.0. No fixed version is listed yet. Memory is accessed after it has been freed, leading to undefined behavior in native code.
How severe is CVE-2024-8375? CVE-2024-8375 has a CVSS score of 6.1 (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 packages are affected by CVE-2024-8375?
- dm-reverb (pip) (versions <= 0.14.0)
- dm-reverb-nightly (pip) (versions <= 0.15.0.dev20240214)
Is there a fix for CVE-2024-8375? No fixed version is listed for CVE-2024-8375 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2024-8375 exploitable, and should I be worried? Whether CVE-2024-8375 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-2024-8375 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-2024-8375? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use memory-safe data structures and address sanitizers during testing.