Memory disclosure or crash via markup over-read
Published May 27, 2022 · Updated Aug 3, 2024
Buffer over-read in libmobi before 0.11 allows local users to disclose process memory or interrupt service through a corrupt Mobipocket file. Markup-search functions in src/parse_rawml.c dereference the current input pointer after scanning to the buffer end because self-closing-tag checks omit an end-boundary or remaining-length guard. Exploitation requires attacker-supplied ebook data to be processed, resulting in unintended memory disclosure or a process crash.
Summary
What happened
Buffer over-read in libmobi before 0.11 allows local users to disclose process memory or interrupt service through a corrupt Mobipocket file. Markup-search functions in src/parse_rawml.c dereference the current input pointer after scanning to the buffer end because self-closing-tag checks omit an end-boundary or remaining-length guard. Exploitation requires attacker-supplied ebook data to be processed, resulting in unintended memory disclosure or a process crash.
The record
- CVE
- CVE-2022-1907
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- bfabiszewski
- Product
- libmobi
- Classifications
- CWE-126
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <0.11
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