NVD / CVE Program· CNA Google

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

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: protocolbuffers protobuf 4.25.0; azl3 mysql 8.0.40-2 on Azure Linux 3.0 8.0.40-2; azl3 mysql 8.0.41-1 on Azure Linux 3.0 8.0.40-2.
Severity is disputed: the assigning authority (CNA) scores it 7.6, NVD 9.8.

Low priority for now. Upgrade to protocolbuffers protobuf 4.25.0; azl3 mysql 8.0.40-2 on Azure Linux 3.0 8.0.40-2; azl3 mysql 8.0.41-1 on Azure Linux 3.0 8.0.40-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: May 3, 2024
Updated: Jun 17, 2026
EPSS: 0.3% · 26th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · Google: 7.6; 2.2 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
google	protobuf	cpe:2.3:a:google:protobuf

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

google protobuf4.22.0 and later · before 4.25.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.

protocolbuffers protobuf
- 4.22.0 and later · before 4.25.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
SUSE:Linux Micro 6.0	protobuf	before 23.4-9.1	23.4-9.1
SUSE:Linux Micro 6.1	protobuf	before 23.4-slfo.1.1_2.1	23.4-slfo.1.1_2.1

Same product

google: all records

Other highest-scoring records for the same primary product.

CVE-2015-5237protobuf allows remote authenticated attackers to cause a heap-based buffer overflow.
36Monitor
CVE-2024-7254Stack overflow in Protocol Buffers Java Lite
35Monitor
CVE-2026-0994Denial of Service in Python Protobuf
32Monitor

Published before and after this one in the same product

← EarlierCVE-2021-22570Jan 26, 2022 · Nullptr Dereference in Protobuf
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
protocolbuffers protobuf	4.25.0	Vendor (CNA)
azl3 mysql 8.0.40-2 on Azure Linux 3.0	8.0.40-2 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 mysql 8.0.41-1 on Azure Linux 3.0	8.0.40-2 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 mysql 8.0.40-2 on CBL Mariner 2.0	8.0.40-2 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 mysql 8.0.41-1 on CBL Mariner 2.0	8.0.40-2 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 mysql 8.0.41-1 on CBL-Mariner 2.0	8.0.40-2 · CBL-Mariner Releases	Microsoft (MSRC)
suse:protobuf	23.4-9.1 · SUSE:Linux Micro 6.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/protocolbuffers/protobuf/releases/tag/v25.0

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records