HighGHSA-jwvw-v7c5-m82hCVE-2015-5237PYSEC-2017-65

protobuf susceptible to buffer overflow

Published 13 May 2022 · Updated 9 Jul 2026

Is your project on an affected Google.Protobuf?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:dotnet add package Google.Protobuf --version 3.4.0
Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=com.google.protobuf:protobuf-parent -DdepVersion=3.4.0 -DforceVersion=true
Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:go get github.com/protocolbuffers/protobuf@v3.4.0
Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:composer require google/protobuf:^3.4.0
Affected
<3.4.0
Fixed in
3.4.0
Update to the fixed version for your release line, for example:pip install 'protobuf>=3.4.0'

Details

protobuf allows remote authenticated attackers to cause a heap-based buffer overflow.

Is GHSA-jwvw-v7c5-m82h in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Google.Protobuf, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.