Skip to content
Fencer Vulns
high 7.6

CVE-2024-2410 json

Use after free in C++ protobuf

published 2024-05-03 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-27362

cvss
7.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

The JsonToBinaryStream() function is part of the protocol buffers C++ implementation and is used to parse JSON from a stream. If the input is broken up into separate chunks in a certain way, the parser will attempt to read bytes from a chunk that has already been freed.

Patch / fix

  • protocolbuffers protobuf 4.25.0
  • google protobuf 4.25.0
  • protobuf Linux Micro 6.1 23.4-slfo.1.1_2.1
  • protobuf Linux Micro 6.0 23.4-9.1

suse advisories SUSE-SU-2025:20672-1SUSE-SU-2025:20155-1

  • mysql CBL-Mariner 2.0, Azure Linux 3.0 8.0.40-2

azure linux advisories AZL-51077AZL-51319

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-2410 updated cvss 7.3

protobuf: Use-after-free in JsonToBinaryStream()

  • Red Hat OpenStack Platform 16.1 protobuf, python3-protobuf Red Hat OpenStack Platform 16.2 protobuf, python3-protobuf
    affected: workaround, no fix planned “Do not parse a JSON input split into separated chunks using the JsonToBinaryStream function.”
  • Red Hat Ansible Automation Platform 2 python-protobuf, python3x-protobuf Red Hat Enterprise Linux 7 protobuf, protobuf-vim, protobuf-java, protobuf-lite, protobuf-emacs, protobuf-python, +3 more Red Hat Enterprise Linux 8 protobuf, protobuf-lite, python3-protobuf, protobuf-compiler Red Hat Enterprise Linux 9 protobuf, fence-virt, fence-virtd, fence-agents, protobuf-lite, fence-virtd-cpg, +55 more Red Hat Enterprise Linux 10 protobuf
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.6 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • protocolbuffers protobuf
  • google protobuf

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.