Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Malicious files can cause the program to enter a large loop #1472

Open
pic4xiu opened this issue Jul 16, 2023 · 5 comments
Open

Malicious files can cause the program to enter a large loop #1472

pic4xiu opened this issue Jul 16, 2023 · 5 comments

Comments

@pic4xiu
Copy link

pic4xiu commented Jul 16, 2023

Maliciously constructed pictures can cause the program to enter a large loop and continuously print warning messages on the terminal.

Expected behavior and actual behavior.

Program file format error, parsing failed~

But the program enters a big loop and keeps printing in the terminal:

...
[WARNING] Not enough space for expected EPH marker
[WARNING] Not enough space for expected SOP marker
[WARNING] Not enough space for expected EPH marker
[WARNING] Not enough space for expected SOP marker
[WARNING] Not enough space for expected EPH marker
[WARNING] Not enough space for expected SOP marker
[WARNING] Not enough space for expected EPH marker
[WARNING] Not enough space for expected SOP marker
...

I tested it with ubuntu, and the program ran for more than 4 hours.

Steps to reproduce the problem.

the poc is here

Run: opj_decompress -i bigloop -o te.raw

Maybe the memory must be at least greater than 8g to ensure successful reproduction.

Operating system

Ubuntu, macos, windows are all available

openjpeg version

OpenJPEG 2.5.0

@pedrohc
Copy link

pedrohc commented Jul 4, 2024

CVE-2023-39327 was assigned to this flaw. If you wish to dispute or reject please let me know.

@fundawang
Copy link

could anyone confirm that this issue was fixed by pull#1547?

@jubalh
Copy link

jubalh commented Sep 18, 2024

@fundawang the POC is mentioned above. Just run it and report back.

@mayeut
Copy link
Collaborator

mayeut commented Sep 18, 2024

The pull request confirms that it's not fixed in its description. A slight modification of the PoC allows to trigger the behavior.

@tariqmchoudhry
Copy link

Does anyone has a work around or a fix ready for this issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants