-
Notifications
You must be signed in to change notification settings - Fork 196
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
Segmentation fault with raster-interpret.c:1055 #831
Comments
Hi @schsiung , thank you for the report! I'm not able to compile your fuzzer due missing deps on Fedora and precompiled version does not work for me, but from the place and function where it crashed I suppose *ptr is NULL (ptr is optimized out and I don't understand assembler well here) and the binary crashes when it tries to dereference it. Then the fix would be:
Can you apply it and tell if it helps? |
@zdohnal I have merged your fix code locally and It looks to be a valid fix for the aforementioned crashes. |
@schsiung Thanks! I'll file PR. |
Fuzzer using `_cupsRasterExecPS()` found a way how to pass NULL into `scan_ps()`, causing crash - we have to sanitize the argument for NULL to fix it. Fixes OpenPrinting#831
Fuzzer using _cupsRasterExecPS() found a way how to pass NULL into scan_ps(), causing crash - we have to sanitize the argument for NULL to fix it. Fixes #831
Fuzzer using `_cupsRasterExecPS()` found a way how to pass NULL into `scan_ps()`, causing crash - we have to sanitize the argument for NULL to fix it. Fixes #831
The same fix as in OpenPrinting/cups#831
Describe the bug
I have found SIGSEGV crashes with cups of version #v2.4.7 when running some fuzzing tests. here is the fuzzing code I use:
fuzzer.tar.gz
FuzzCUPS.c
To Reproduce
Steps to reproduce the behavior:
cups
and runmake
./FuzzCUPS < out1/default/crashes/id:000051,sig:11,src:000906,time:819791,execs:36265773,op:havoc,rep:3
Expected behavior
add proper validations for the misused inputs and display the right error message
System Information:
From
From: xiongshengchao@jyhlab.org.cn
The text was updated successfully, but these errors were encountered: