Panic when parsing invalid messages in google.golang.org/protobuf
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| google.golang.org/protobuf | google.golang.org/protobuf/encoding/prototext | unaffected |
|
||||||
| google.golang.org/protobuf | google.golang.org/protobuf/internal/encoding/text | unaffected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-1039 | Parsing invalid messages can panic. Parsing a text-format message which contains a potential number consisting of a minus sign, one or more characters of whitespace, and no further input will cause a panic. |
Github GHSA |
GHSA-hw7c-3rfg-p46j | google.golang.org/protobuf vulnerable to panic leading to denial of service |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.089% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|