First published: Wed Jan 01 2025(Updated: )
This bug is triggered when we use opj_decompress with the -t option and its argument set to 1. The latest version v2.5.2 also has this vulnerability. Reproducible: Always Steps to Reproduce: see <a href="https://github.com/uclouvain/openjpeg/issues/1564">https://github.com/uclouvain/openjpeg/issues/1564</a> References: <a href="https://github.com/uclouvain/openjpeg/issues/1564">https://github.com/uclouvain/openjpeg/issues/1564</a> <a href="https://github.com/uclouvain/openjpeg/commit/e492644fbded4c820ca55b5e50e598d346e850e8">https://github.com/uclouvain/openjpeg/commit/e492644fbded4c820ca55b5e50e598d346e850e8</a>
Affected Software | Affected Version | How to fix |
---|---|---|
uclouvain openjpeg |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2335174 is critical due to the potential for exploitation when using opj_decompress with the -t option.
To fix REDHAT-BUG-2335174, update to the latest version of OpenJPEG that addresses this specific bug.
All versions of OpenJPEG up to and including v2.5.2 are affected by REDHAT-BUG-2335174.
The vulnerability in REDHAT-BUG-2335174 is triggered when using opj_decompress with the -t option set to 1.
There is currently no known workaround for REDHAT-BUG-2335174 other than applying the available updates.