Service interruption via unreleased MAT-file allocations
Published May 2, 2022 · Updated Aug 3, 2024
Memory leak in Mat_VarReadNextInfo5 in Matio 1.5.21 and earlier allows local users to exhaust memory through a crafted MAT file. The v5 MAT-file parser fails to release variable structures, dimensions, and names allocated during recursive function-handle parsing. Exploitation requires an application using the library to process the file; repeated parsing can exhaust process memory and interrupt that application.
Summary
What happened
Memory leak in Mat_VarReadNextInfo5 in Matio 1.5.21 and earlier allows local users to exhaust memory through a crafted MAT file. The v5 MAT-file parser fails to release variable structures, dimensions, and names allocated during recursive function-handle parsing. Exploitation requires an application using the library to process the file; repeated parsing can exhaust process memory and interrupt that application.
The record
- CVE
- CVE-2022-1515
- Published
- May 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Matio Project
- Product
- Matio
- Classifications
- CWE-401, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 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=matio 1.5.22, matio 1.5.23
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
- Mat_VarReadNextInfo5 crafted-file reproducerproof 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