Memory corruption via uncleared oneof pointer
Published Mar 23, 2021 · Updated Aug 3, 2024
Memory corruption in Nanopb 0.3.2 through 0.3.9.7 and 0.4.0 through 0.4.4 allows attackers to crash applications via crafted messages. In pb_release_union_field, the decoder switches from a non-pointer oneof member to a pointer member without clearing the union storage, then passes attacker-controlled data to free() or realloc(). The path requires PB_ENABLE_MALLOC and a oneof containing pointer and non-pointer fields; the consequence ranges from an application crash to heap corruption.
Summary
What happened
Memory corruption in Nanopb 0.3.2 through 0.3.9.7 and 0.4.0 through 0.4.4 allows attackers to crash applications via crafted messages. In pb_release_union_field, the decoder switches from a non-pointer oneof member to a pointer member without clearing the union storage, then passes attacker-controlled data to free() or realloc(). The path requires PB_ENABLE_MALLOC and a oneof containing pointer and non-pointer fields; the consequence ranges from an application crash to heap corruption.
The record
- CVE
- CVE-2021-21401
- Published
- Mar 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- Petteri Aimonen
- Product
- Nanopb
- Classifications
- CWE-763, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=>= 0.3.2, <= 0.3.9.7
- Affected versionversion=>= 0.4.0, <= 0.4.4
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.
Weakness, pattern, technique
Public exploit references
- Minimal crafted oneof message reproducerproof of concept · demonstrated
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