Memory corruption via unchecked sparse-matrix indexes
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in LIBXSMM through 1.16.1-93 allows context-dependent attackers to corrupt memory via crafted sparse-matrix input. The CSC and CSR readers accept row, column, and element indexes from an MTX file without checking them against allocated array bounds. A consuming application must pass attacker-controlled matrix data to the static JIT generator, where the out-of-bounds writes can crash the process or corrupt its memory.
Summary
What happened
Heap-based buffer overflow in LIBXSMM through 1.16.1-93 allows context-dependent attackers to corrupt memory via crafted sparse-matrix input. The CSC and CSR readers accept row, column, and element indexes from an MTX file without checking them against allocated array bounds. A consuming application must pass attacker-controlled matrix data to the static JIT generator, where the out-of-bounds writes can crash the process or corrupt its memory.
The record
- CVE
- CVE-2021-39536
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 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.
Public exploit references
- LIBXSMM issue 402 reproducerproof 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