Application crash via uncaught parser exceptions
Published Feb 24, 2022 · Updated Aug 3, 2024
Improper exception handling in metadata-extractor 2.16.0 and earlier allows context-dependent attackers to crash applications via a crafted JPEG. The upstream crash corpus identifies 33 parser paths where malformed values trigger uncaught arithmetic, bounds, allocation, null, or string exceptions. Exploitation requires a consuming application to process attacker-supplied image data; an escaping exception can terminate that application or an exposed service.
Summary
What happened
Improper exception handling in metadata-extractor 2.16.0 and earlier allows context-dependent attackers to crash applications via a crafted JPEG. The upstream crash corpus identifies 33 parser paths where malformed values trigger uncaught arithmetic, bounds, allocation, null, or string exceptions. Exploitation requires a consuming application to process attacker-supplied image data; an escaping exception can terminate that application or an exposed service.
The record
- CVE
- CVE-2022-24613
- Published
- Feb 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Crash seeds and reproduction programproof 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