Process crash or code execution via freed memory
Published Nov 15, 2021 · Updated Apr 23, 2025
Use-after-free in BusyBox awk before 1.34.0 allows attackers to crash its process or possibly execute code through a crafted pattern. The evaluate function accesses freed memory while processing an attacker-controlled awk program. Exploitation requires control of the awk program argument; a crash normally terminates only the forked applet process.
Summary
What happened
Use-after-free in BusyBox awk before 1.34.0 allows attackers to crash its process or possibly execute code through a crafted pattern. The evaluate function accesses freed memory while processing an attacker-controlled awk program. Exploitation requires control of the awk program argument; a crash normally terminates only the forked applet process.
The record
- CVE
- CVE-2021-42383
- Published
- Nov 15, 2021
- Updated
- Apr 23, 2025
- Vendor
- BusyBox
- Product
- BusyBox
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 15, 2021CVE publishedPublication date reported by the CVE source.
- Apr 23, 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 <1.34.0
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.
Weakness, pattern, technique
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