OSV-2025-1049 Heap-buffer-overflow in unsigned char* std::__1::vector<unsigned char, std::__1::allocator<unsigned char

Not scored Published

A heap buffer overflow in the pcpp library allows attackers to cause a denial of service via crafted TLS Client Hello messages.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is OSV-2025-1049?

OSV-2025-1049 is a memory corruption vulnerability in pcapplusplus, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=472222304

Crash type: Heap-buffer-overflow READ 1
Crash state:
unsigned char* std::__1::vector&lt;unsigned char, std::__1::allocator&lt;unsigned char
pcpp::TLSECPointFormatExtension::getECPointFormatList
pcpp::SSLClientHelloMessage::generateTLSFingerprint

Which versions are affected by OSV-2025-1049?

1 open source package ship an affected version, including pcapplusplus.

PackageAffectedFixed in
pcapplusplus OSS-FuzzAll versionsNone

How do I fix OSV-2025-1049?

No fix has been published for OSV-2025-1049 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is OSV-2025-1049 being exploited?

There is no known exploitation of OSV-2025-1049 in the wild and no public exploit code.

Sources

Is OSV-2025-1049 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free