Heap-based Buffer Overflow in protobuf

protobuf Updated 02 Oct 2025

Summary

25/09/2017
N/A
No i
High
8.8

CVE-2015-5237: protobuf allows remote authenticated attackers to cause a heap-based buffer overflow. Affects protobuf versions 3.12.4-1 – 4.0.0~rc2-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Protobuf is a popular open-source library used for serializing structured data. It provides an efficient and flexible way to encode and decode data in various programming languages. However, the library is vulnerable to a heap-based buffer overflow, which can be exploited by remote authenticated attackers.

Vulnerability Detail

The vulnerability, identified as CVE-2015-5237, allows attackers to trigger a heap-based buffer overflow in protobuf. This can lead to arbitrary code execution or denial of service attacks. The issue originates from a flaw in the library's handling of certain input data, which can be exploited to overwrite adjacent memory locations.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the protobuf library to a version that includes a patch for CVE-2015-5237. The maintainers of the library have addressed this issue in subsequent releases, so upgrading to the latest stable version should resolve the problem.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If updating the library is not immediately feasible, a possible workaround is to implement input validation and sanitization in the application code that uses protobuf. By carefully validating and filtering input data, the risk of triggering the buffer overflow can be mitigated.

Conclusion

In conclusion, the protobuf library is vulnerable to a heap-based buffer overflow, which can be exploited by remote authenticated attackers. It is crucial to update the library to a patched version or implement input validation to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for protobuf →

Share this vulnerability

FAQ

Protobuf, short for Protocol Buffers, is an open-source library for serializing structured data.

A heap-based buffer overflow occurs when a program writes data beyond the allocated memory buffer on the heap, potentially overwriting adjacent memory locations.

Remote authenticated attackers can exploit this vulnerability by providing specially crafted input data to the protobuf library, triggering the heap-based buffer overflow.

The vulnerability can lead to arbitrary code execution or denial of service attacks, depending on how it is exploited.

Yes, updating the protobuf library to a version that includes the patch for CVE-2015-5237 is the recommended fix.

Related vulnerabilities

Recent vulnerabilities recorded for protobuf.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the protobuf library to a version that includes a patch for CVE-2015-5237. The maintainers of the library have addressed this issue in subsequent releases, so upgrading to the latest stable version should resolve the problem.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.