Code execution via out-of-bounds WAV parsing
Published Nov 22, 2021 · Updated Sep 17, 2024
Memory corruption in Adobe Prelude 10.1 and earlier allows attackers to execute code when a user opens a malicious WAV file. Prelude's WAV parser accesses a memory location after the end of a buffer while handling crafted audio data. Exploitation requires a user to open the file and runs attacker-controlled code with the privileges of the current user.
Summary
What happened
Memory corruption in Adobe Prelude 10.1 and earlier allows attackers to execute code when a user opens a malicious WAV file. Prelude's WAV parser accesses a memory location after the end of a buffer while handling crafted audio data. Exploitation requires a user to open the file and runs attacker-controlled code with the privileges of the current user.
The record
- CVE
- CVE-2021-40771
- Published
- Nov 22, 2021
- Updated
- Sep 17, 2024
- Vendor
- Adobe
- Product
- Adobe Prelude
- Classifications
- CWE-788, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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 <=10.1
- Affected versionversion=unspecified <=None
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
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