Skip to content

← Actionable
Medium, CVSS 5.7amended

Reverb use after free vulnerability

CVE-2024-8375GHSA-w69q-w4h4-2fx8

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI dm-reverb-nightly

    Affected
    <= 0.15.0.dev20240214
    Fixed in
    no fixed version recorded
  • PyPI dm-reverb

    Affected
    <= 0.14.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.7 · CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source
EPSS
  • CVE-2024-8375: 0.12% estimated exploitation activity in the next 30 days; percentile 2.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 tensorcontent to the previously mentioned pre-allocated memory, which results in the bytes in tensorcontent 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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-w69q-w4h4-2fx8

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-w69q-w4h4-2fx8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-8375

Advisory: Reverb use after free vulnerability
IDs: CVE-2024-8375, GHSA-w69q-w4h4-2fx8
Record: https://patchnext.com/advisories/cve-2024-8375 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dm-reverb-nightly: affected <= 0.15.0.dev20240214
- PyPI dm-reverb: affected <= 0.14.0

## Suggested inspection (read-only)
- `python -m pip show dm-reverb-nightly`: prints the installed version. Run with the environment that serves production active.
- `python -m pip show dm-reverb`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dm-reverb-nightly, dm-reverb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w69q-w4h4-2fx8 (OSV record GHSA-w69q-w4h4-2fx8 lists affected ranges: PyPI dm-reverb >=0 =0 <=0.15.0.dev20240214)
- Verified: https://github.com/advisories/GHSA-w69q-w4h4-2fx8 (GitHub-reviewed advisory GHSA-w69q-w4h4-2fx8 lists affected ranges: PyPI dm-reverb >=0 =0 <=0.15.0.dev20240214)

Commands are suggestions: review each one before running it.

Loading voting…