Local code execution via filename overflow
Published Feb 26, 2021 · Updated Sep 16, 2024
FAAD2 before 2.2.7.1 allows local attackers to execute arbitrary code through crafted filename and pathname options. In frontend/main.c, fixed 255-byte stack buffers formerly received option and input-path strings with unchecked strcpy operations, so oversized names overwrite stack memory. Exploitation requires local execution of the faad frontend with attacker-controlled filename or pathname arguments and can compromise confidentiality, integrity, and availability.
Summary
What happened
FAAD2 before 2.2.7.1 allows local attackers to execute arbitrary code through crafted filename and pathname options. In frontend/main.c, fixed 255-byte stack buffers formerly received option and input-path strings with unchecked strcpy operations, so oversized names overwrite stack memory. Exploitation requires local execution of the faad frontend with attacker-controlled filename or pathname arguments and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-26567
- Published
- Feb 26, 2021
- Updated
- Sep 16, 2024
- Vendor
- Nero AG
- Product
- FAAD2
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=unspecified <2.2.7.1
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