Local memory corruption via stale comment buffer
Published Jan 20, 2023 · Updated Apr 3, 2025
Use-after-free in Berkeley Yacc allows local users to corrupt process memory by supplying a crafted grammar file for processing. The file reader frees the allocation holding the current input line, but comment processing later dereferences that stale buffer. A user must invoke BYACC on attacker-controlled grammar input, after which the invalid access can crash the process or alter its memory.
Summary
What happened
Use-after-free in Berkeley Yacc allows local users to corrupt process memory by supplying a crafted grammar file for processing. The file reader frees the allocation holding the current input line, but comment processing later dereferences that stale buffer. A user must invoke BYACC on attacker-controlled grammar input, after which the invalid access can crash the process or alter its memory.
The record
- CVE
- CVE-2021-33641
- Published
- Jan 20, 2023
- Updated
- Apr 3, 2025
- Vendor
- Thomas E. Dickey
- Product
- Berkeley Yacc (BYACC)
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=<1.9.20200330 and <2.0.20210808
What conditions does exploitation require?
What is affected?
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