Application crash via wrapped filename-buffer allocation
Published Apr 14, 2021 · Updated Nov 3, 2025
Integer overflow in OpenJPEG 2.4.0 allows context-dependent attackers to crash opj_compress through a 1,048,576-file directory. The load_images path multiplies num_images by OPJ_PATH_LEN in an integer-sized expression, wrapping the filename-buffer allocation to zero before strcpy copies entries beyond it. A local user must invoke opj_compress with -ImgDir on the populated directory; the demonstrated consequence is a process crash.
Summary
What happened
Integer overflow in OpenJPEG 2.4.0 allows context-dependent attackers to crash opj_compress through a 1,048,576-file directory. The load_images path multiplies num_images by OPJ_PATH_LEN in an integer-sized expression, wrapping the filename-buffer allocation to zero before strcpy copies entries beyond it. A local user must invoke opj_compress with -ImgDir on the populated directory; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2021-29338
- Published
- Apr 14, 2021
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2021CVE 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?
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
- OpenJPEG 1,048,576-file directory 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