Process crash via stale considered-map index
Published May 18, 2021 · Updated Aug 3, 2024
Heap buffer overflow in openSUSE libsolv before 0.7.17 allows local users to crash testsolv by loading a crafted testcase file. The function creates pool->considered before later repository directives can add solvables, then MAPCLR indexes that stale bitmap with p >> 3 without checking its size. A user must cause testsolv to parse a crafted testcase; the demonstrated consequence is an out-of-bounds heap access and process abort.
Summary
What happened
Heap buffer overflow in openSUSE libsolv before 0.7.17 allows local users to crash testsolv by loading a crafted testcase file. The function creates pool->considered before later repository directives can add solvables, then MAPCLR indexes that stale bitmap with p >> 3 without checking its size. A user must cause testsolv to parse a crafted testcase; the demonstrated consequence is an out-of-bounds heap access and process abort.
The record
- CVE
- CVE-2021-3200
- Published
- May 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2021CVE 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.
Weakness, pattern, technique
Public exploit references
- PoC-testcase_read-2334proof 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