Nullptr Dereference in Protobuf
Google LLC Protobuf
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Google.Protobuf NuGet |
|
|
| google/protobuf Packagist |
|
|
| com.google.protobuf:protobuf-java Maven |
Google LLC Protobuf
| Product | Affected | Fixed in |
|---|---|---|
| Google.Protobuf NuGet |
|
|
| google/protobuf Packagist |
|
|
| com.google.protobuf:protobuf-java Maven |
|
|
| github.com/protocolbuffers/protobuf Go |
|
|
| protobuf PyPI |
|
|
Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr. We recommend upgrading to version 3.15.0 or greater.
From the CVE record · Google
A null character in a proto symbol can cause incorrect parsing and a null-pointer dereference while generating an error message. The input does not establish whether an attacker can supply the symbol or whether network access, authentication, or user interaction is required.
Teams using Google.Protobuf on NuGet, google/protobuf on Packagist, protobuf-java on Maven, or protobuf on PyPI below 3.15.0, or affected github.com/protocolbuffers/protobuf versions on Go, should check their dependencies.