Memory corruption via out-of-bounds write in play
Published Sep 15, 2022 · Updated Aug 3, 2024
Out-of-bounds write in MPlayer and MEncoder SVN-r38374-13.0.1 allows attackers to corrupt memory during media processing. The play() function at libaf/af.c line 639 writes past the intended buffer while the audio-filter path processes data. Triggering requires local execution and user interaction; public records do not establish whether the result is limited to a crash or enables code execution.
Summary
What happened
Out-of-bounds write in MPlayer and MEncoder SVN-r38374-13.0.1 allows attackers to corrupt memory during media processing. The play() function at libaf/af.c line 639 writes past the intended buffer while the audio-filter path processes data. Triggering requires local execution and user interaction; public records do not establish whether the result is limited to a crash or enables code execution.
The record
- CVE
- CVE-2022-38862
- Published
- Sep 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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