Compiler crash via malformed diagnostic argument
Published Jul 18, 2023 · Updated Oct 28, 2024
NULL pointer dereference in asn1c 0.9.28 and earlier allows local users to crash the compiler with a crafted ASN.1 file. While fixing an ENUM definition, asn1f_fix_enum passes a malformed diagnostic argument to _default_error_logger, whose vfprintf path reads address 0x1 as a string. The user must run the semantic-fixing stage on the file; the demonstrated consequence is termination of that compiler process, not code execution or data disclosure.
Summary
What happened
NULL pointer dereference in asn1c 0.9.28 and earlier allows local users to crash the compiler with a crafted ASN.1 file. While fixing an ENUM definition, asn1f_fix_enum passes a malformed diagnostic argument to _default_error_logger, whose vfprintf path reads address 0x1 as a string. The user must run the semantic-fixing stage on the file; the demonstrated consequence is termination of that compiler process, not code execution or data disclosure.
The record
- CVE
- CVE-2020-23911
- Published
- Jul 18, 2023
- Updated
- Oct 28, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 18, 2023CVE publishedPublication date reported by the CVE source.
- Oct 28, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Upstream crash proof of conceptproof 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