Process-memory disclosure via uninitialized format write
Published May 4, 2022 · Updated Aug 3, 2024
Use of uninitialized data in wav_format_write in libwav through 2017-04-20 allows attackers to disclose process memory in WAV output. The function passes the entire wav_format structure to fwrite, including bytes left uninitialized, so residual process memory enters the output stream. Exploitation requires a caller to process attacker-controlled WAV data and expose the generated output; the demonstrated consequence is memory disclosure.
Summary
What happened
Use of uninitialized data in wav_format_write in libwav through 2017-04-20 allows attackers to disclose process memory in WAV output. The function passes the entire wav_format structure to fwrite, including bytes left uninitialized, so residual process memory enters the output stream. Exploitation requires a caller to process attacker-controlled WAV data and expose the generated output; the demonstrated consequence is memory disclosure.
The record
- CVE
- CVE-2022-28488
- Published
- May 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-908, T1005
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 4, 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.
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
- tin-z libwav proof of conceptproof of concept · demonstrated
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