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

Failed-Assertion-in jasper(version 3.0.6, commit 66632500) #345

Closed
benehalo opened this issue Oct 11, 2022 · 5 comments
Closed

Failed-Assertion-in jasper(version 3.0.6, commit 66632500) #345

benehalo opened this issue Oct 11, 2022 · 5 comments
Assignees

Comments

@benehalo
Copy link

Crash Inputs

Here are the files that trigger the bug - jas_image.c_1010.zip

Bug Description

I apply debug mode (-g -O0) to check for errors and report the detected errors as follows.

jasper: /data/code/jasper/src/libjasper/base/jas_image.c:1010: uint_fast32_t inttobits(jas_seqent_t, unsigned int, _Bool): Assertion `v >= 0 || sgnd' failed.

How to Reproduce

The aforementioned bug can be stably reproduced in version 3.0.6 (commit id 6663250).

  1. Download the jasper source code with the [official link](https://github.com/mdadams/jasper).
  2. Using clang/clang++ (10.0.0-4ubuntu1), build jasper with debug mode.
    • -g -O0
  3. Execute jasper with the provided input files.
    • eg: /data/program/jasper/test/bin/jasper --input <input-file-path> --output /tmp/test.bmp --output-format bmp
@jubalh
Copy link
Member

jubalh commented Oct 11, 2022

You have 5 files in the zip file, each of them triggers the same response, yes?

@benehalo
Copy link
Author

benehalo commented Oct 12, 2022

You have 5 files in the zip file, each of them triggers the same response, yes?

Yes, each of the input files triggers the same reponse.

@jubalh
Copy link
Member

jubalh commented Oct 12, 2022

Thanks for confirming.

@AHMorinaga
Copy link

What is the range of Jasper versions that contain this vulnerability?

@jubalh
Copy link
Member

jubalh commented Dec 1, 2022

You'll have to check that yourself unfortunately.
3.0.6 is vulnerable and 4.0.0 is the first version with the fix.

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

4 participants