Process crash via stale considered bitmap
Published Sep 2, 2021 · Updated Aug 4, 2024
Heap-buffer overflow in libsolv before 0.7.17 allows attackers to crash a consuming process through crafted testcase input. The testcase_read parser can add solvables after pool->considered is allocated, causing pool_installable to index beyond the stale bitmap. Triggering the defect requires a consumer to parse attacker-controlled testcase data; the demonstrated consequence is process termination only.
Summary
What happened
Heap-buffer overflow in libsolv before 0.7.17 allows attackers to crash a consuming process through crafted testcase input. The testcase_read parser can add solvables after pool->considered is allocated, causing pool_installable to index beyond the stale bitmap. Triggering the defect requires a consumer to parse attacker-controlled testcase data; the demonstrated consequence is process termination only.
The record
- CVE
- CVE-2021-33928
- Published
- Sep 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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-pool_disabled_solvable-line96proof 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