Compiler crash via null-character proto symbol
Published Jan 26, 2022 · Updated Apr 21, 2025
Null pointer dereference in Google Protocol Buffers before 3.15.0 allows attackers to crash protoc with a null-containing proto symbol. The symbol parser misclassifies the input, leaves the associated file pointer null, and dereferences it while formatting an error through the file-name accessor. The attacker must cause an affected C++ compiler invocation to process the crafted symbol; the bounded consequence is termination of that compiler process.
Summary
What happened
Null pointer dereference in Google Protocol Buffers before 3.15.0 allows attackers to crash protoc with a null-containing proto symbol. The symbol parser misclassifies the input, leaves the associated file pointer null, and dereferences it while formatting an error through the file-name accessor. The attacker must cause an affected C++ compiler invocation to process the crafted symbol; the bounded consequence is termination of that compiler process.
The record
- CVE
- CVE-2021-22570
- Published
- Jan 26, 2022
- Updated
- Apr 21, 2025
- Vendor
- Product
- Protocol Buffers
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <3.15.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo