Memory disclosure and crash via markup boundary error
Published May 27, 2022 · Updated Aug 3, 2024
Buffer over-read in libmobi before 0.11 allows local users to read adjacent memory or crash an application via a corrupt ebook. The markup scanners in src/parse_rawml.c dereference the current input pointer after a scan reaches its boundary because three self-closing-tag checks lack an end-of-buffer guard. A local user must cause a person to open a crafted Mobipocket file; the resulting out-of-bounds read can expose process memory or terminate the consuming application.
Summary
What happened
Buffer over-read in libmobi before 0.11 allows local users to read adjacent memory or crash an application via a corrupt ebook. The markup scanners in src/parse_rawml.c dereference the current input pointer after a scan reaches its boundary because three self-closing-tag checks lack an end-of-buffer guard. A local user must cause a person to open a crafted Mobipocket file; the resulting out-of-bounds read can expose process memory or terminate the consuming application.
The record
- CVE
- CVE-2022-1908
- Published
- May 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- bfabiszewski
- Product
- libmobi
- Classifications
- CWE-126, CWE-125, T1203
- 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?
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
- huntr.dev crafted-input proof of conceptproof of concept · unverified
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