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
SEGV caused by a READ memory access #107
Comments
|
Both examples seem to point issue in libjpeg.so.8 (what was the exact version of libjpeg that jpegoptim was linked against?) |
|
I use |
|
Was registered as CVE-2022-32325 |
|
How exactly is this an issue in jpegoptim? Stack traces clearly show issue in libjpeg.so.8, and not in jpegoptim.... or am I missing something? |
|
I would suggest to check and reproduce it with a newer |
|
Unable to reproduce with the current 'master' branch (tested with currently latest libjpeg version "9e"): It could be that this was fixed by change 3401f25. Can you validate if you can still reproduce issue with the latest version from github? |
hi, with the help of fuzzing ,I found some crash sample in this repo, here is the sample, are they new bugs?
crash position jpegoptim.c:631:3
crash sample: crash1_SEGV_caused_by_READ_memory_access_at_jpegoptim.c:631:3
sample here:
crash1_SEGV_caused_by_READ_memory_access_at_jpegoptim.zip
command: ./jpegoptim -f --all-progressive crash_sample
crash position: jpegoptim.c:710:18
crash sample: crash2_SEGV_caused_by_READ_memory_access_at_jpegoptim.c:710:18
sample here:
crash_SEGV_caused_by_READ_memory_access_at_jpegoptim.zip
command: ./jpegoptim -f --all-progressive crash_sample
The text was updated successfully, but these errors were encountered: