cve.bz

CVE-2024-2410 google protobuf: Use After Free

9.8 criticalEPSS 0.3%

Critical (9.8) in google protobuf. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-06-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-2410 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-2410?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-2410?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-2410 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
protocolbuffers protobuffrom 4.22.0 before 4.25.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Micro 6.0protobuf23.4-9.1SUSE-SU-2025:20155-1
SUSELinux Micro 6.1protobuf23.4-slfo.1.1_2.1SUSE-SU-2025:20672-1
Azure Linux2mysql8.0.40-2AZL-51077
Azure Linux3mysql8.0.40-2AZL-51319
Alpaquita23protobufno fix listedBELL-CVE-2024-2410
Alpaquitastreamprotobuf25.6-r0BELL-CVE-2024-2410
BellSoft Hardened Containersstreamprotobuf25.6-r0BELL-CVE-2024-2410

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The protobuf package, as shipped in Red Hat Enterprise Linux 7, 8 and 9, is not affected by this vulnerability because the vulnerable code was introduced in a newer version of protobuf.

Red Hat's mitigation

Do not parse a JSON input split into separated chunks using the JsonToBinaryStream function.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2python3x-protobufNot affected
Red Hat Ansible Automation Platform 2python-protobufNot affected
Red Hat Enterprise Linux 10protobufNot affected
Red Hat Enterprise Linux 7protobufNot affected
Red Hat Enterprise Linux 8protobufNot affected
Red Hat Enterprise Linux 9fence-agentsNot affected
Red Hat Enterprise Linux 9protobufNot affected
Red Hat OpenStack Platform 16.1protobufOut of support scope
Red Hat OpenStack Platform 16.2protobufWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-2410.

References

Check your stackJSON