Memory disclosure or crash via unchecked inflection index
Published Apr 29, 2022 · Updated Aug 3, 2024
Buffer over-read in libmobi before 0.11 allows local users to disclose process memory or crash an application via a corrupt ebook. mobi_reconstruct_infl uses an unvalidated parts[j] value to index infl->entries while reconstructing inflection rules from malformed input. Exploitation requires an application to parse an attacker-controlled ebook, exposing adjacent process memory or terminating the host application.
Summary
What happened
Buffer over-read in libmobi before 0.11 allows local users to disclose process memory or crash an application via a corrupt ebook. mobi_reconstruct_infl uses an unvalidated parts[j] value to index infl->entries while reconstructing inflection rules from malformed input. Exploitation requires an application to parse an attacker-controlled ebook, exposing adjacent process memory or terminating the host application.
The record
- CVE
- CVE-2022-1534
- Published
- Apr 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- bfabiszewski
- Product
- libmobi
- Classifications
- CWE-125, CWE-126
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 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.
Public exploit references
- huntr.dev proof-of-concept artifactproof 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