Advisories
For your digest

Google.Protobuf, com.google.protobuf:protobuf-parent: protobuf susceptible to buffer overflow

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • Google.Protobuf (NuGet): every version, before 3.4.0
  • com.google.protobuf:protobuf-parent (Maven): every version, before 3.4.0
  • github.com/protocolbuffers/protobuf (Go): every version, before 3.4.0
  • google/protobuf (Packagist): every version, before 3.4.0
  • protobuf (PyPI): every version, before 3.4.0
  • protobuf (PyPI): every version, before 3.4.0

The fix

  • Google.Protobuf (NuGet) fixed in 3.4.0

    dotnet
    dotnet add package Google.Protobuf --version 3.4.0
    Check what is installed
    dotnet list package
    Paste into Cursor, Lovable or Claude Code
    Upgrade the NuGet dependency Google.Protobuf to 3.4.0 or the nearest later release, to fix CVE-2015-5237. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • com.google.protobuf:protobuf-parent (Maven) fixed in 3.4.0

    maven
    mvn versions:use-dep-version -Dincludes=com.google.protobuf:protobuf-parent -DdepVersion=3.4.0 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=com.google.protobuf:protobuf-parent
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency com.google.protobuf:protobuf-parent to 3.4.0 or the nearest later release, to fix CVE-2015-5237. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • github.com/protocolbuffers/protobuf (Go) fixed in 3.4.0

    go
    go get github.com/protocolbuffers/protobuf@v3.4.0
    Check what is installed
    go list -m github.com/protocolbuffers/protobuf
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/protocolbuffers/protobuf to 3.4.0 or the nearest later release, to fix CVE-2015-5237. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • google/protobuf (Packagist) fixed in 3.4.0

    composer
    composer require "google/protobuf:^3.4.0" --update-with-all-dependencies
    Check what is installed
    composer show google/protobuf
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Packagist dependency google/protobuf to 3.4.0 or the nearest later release, to fix CVE-2015-5237. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • protobuf (PyPI) fixed in 3.4.0

    pip
    python -m pip install protobuf==3.4.0
    uv
    uv add protobuf==3.4.0
    poetry
    poetry add protobuf@3.4.0
    Check what is installed
    python -m pip show protobuf
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency protobuf to 3.4.0 or the nearest later release, to fix CVE-2015-5237. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".