CVE-2024-2410 | Use after free in C++ protobuf

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. 

Published: 2024-05-03 Last update: 2025-07-22 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-2410 is rated Low Risk (35.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-2410

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.19% 0.05% -0.14%
2 2025-11-18 0.07% 0.19% +0.12%
3 2025-06-11 0.07%

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-2410

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.8 4.7 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 5.9 [email protected]

Weakness enumeration for CVE-2024-2410

OS Trackers for CVE-2024-2410

vendor priority summary link
debian unimportant CVE-2024-2410 unimportant priority: Debian including 1 source packages (protobuf), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-2410
redhat medium https://access.redhat.com/security/cve/CVE-2024-2410
suse high CVE-2024-2410 severity important: SUSE including 54 source package names (curl-8.14.1-slfo.1.1_1.1, latest:curl-8.14.1-slfo.1.1_1.1, …), 370 product×package rows across 83 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (83 product lines)): Known Not Affected 238, Fixed 132. https://www.suse.com/security/cve/CVE-2024-2410/
ubuntu medium CVE-2024-2410 medium priority: Ubuntu including 1 source packages (protobuf), 9 status rows across 9 suites (bionic, focal, jammy, mantic, noble, oracular, trusty, upstream, xenial): not-affected 8, released 1. https://ubuntu.com/security/CVE-2024-2410

Affected software / configurations for CVE-2024-2410

Vendor Product Version Raw CPE
google protobuf >= 4.22.0, < 4.25.0 cpe:2.3:a:google:protobuf:*:*:*:*:*:*:*:*

References for CVE-2024-2410

cvelogic Threat Intelligence