Utility crash via uninitialized filename pointer free
Published Mar 29, 2022 · Updated Nov 3, 2025
Improper initialization in OpenJPEG opj_decompress 2.4.0 and earlier allows local users to crash the utility through a large input directory. After filename-buffer allocation fails, src/bin/jp2/opj_decompress.c frees dirptr->filename without initializing that pointer. Exploitation requires a user to process an input directory large enough to exhaust the allocation, terminating only that opj_decompress process.
Summary
What happened
Improper initialization in OpenJPEG opj_decompress 2.4.0 and earlier allows local users to crash the utility through a large input directory. After filename-buffer allocation fails, src/bin/jp2/opj_decompress.c frees dirptr->filename without initializing that pointer. Exploitation requires a user to process an input directory large enough to exhaust the allocation, terminating only that opj_decompress process.
The record
- CVE
- CVE-2022-1122
- Published
- Mar 29, 2022
- Updated
- Nov 3, 2025
- Vendor
- Université catholique de Louvain
- Product
- OpenJPEG
- Classifications
- CWE-824, CWE-665, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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=openjpeg2 version 2.4.0 and prior
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
- opj_decompress large-directory crash proof of conceptproof 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