Bug 1485274 - There is a reachable assertion abort in function jpc_dec_process_sot() of JasPer that will lead to remote denial of service attack.
Summary: There is a reachable assertion abort in function jpc_dec_process_sot() of Jas...
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jasper
Version: 7.5-Alt
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Josef Ridky
QA Contact: Desktop QE
URL:
Whiteboard:
Keywords: Security
Depends On:
Blocks: CVE-2017-13745
TreeView+ depends on / blocked
 
Reported: 2017-08-25 09:12 UTC by owl337
Modified: 2019-06-28 07:22 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2019-06-28 07:22:32 UTC


Attachments (Terms of Use)
Triggered by "./imginfo -f POC2" (240 bytes, application/x-rar)
2017-08-25 09:12 UTC, owl337
no flags Details

Description owl337 2017-08-25 09:12:09 UTC
Created attachment 1318058 [details]
Triggered by  "./imginfo -f POC2"

Description of problem:

There is a reachable assertion abort in function jpc_dec_process_sot() of JasPer that will lead to remote denial of service attack.


Version-Release number of selected component (if applicable):

<= latest version

How reproducible:

./imginfo -f POC2


Steps to Reproduce:

$ ./imginfo -f POC2
Aborted (core dumped)

The gdb debugging information is listed below:
(gdb) set args POC2
(gdb) r 
...

Breakpoint 2, jpc_dec_process_sot (dec=<optimized out>, ms=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:515
515					abort();
(gdb) list 
510			  the main header? */
511			if (dec->ppmstab) {
512				/* Convert the PPM marker segment data into a collection of streams
513				  (one stream per tile-part). */
514				if (!(dec->pkthdrstreams = jpc_ppmstabtostreams(dec->ppmstab))) {
515					abort();
516				}
517				jpc_ppxstab_destroy(dec->ppmstab);
518				dec->ppmstab = 0;
519			}
(gdb) bt
#0  jpc_dec_process_sot (dec=<optimized out>, ms=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:515
#1  0x00007ffff7b49ceb in jpc_dec_decode (dec=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:424
#2  jpc_decode (in=<optimized out>, optstr=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:261
#3  0x00007ffff7b059ce in jas_image_decode (in=<optimized out>, fmt=<optimized out>, optstr=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/base/jas_image.c:442
#4  0x0000000000401bab in main (argc=<optimized out>, argv=<optimized out>)
    at /home/icy/secreal/jasper/src/appl/imginfo.c:238

Program received signal SIGABRT, Aborted.
0x00007ffff71f8428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
54	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) 

jpc_dec_process_sot (dec=<optimized out>, ms=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:515
510			  the main header? */
511			if (dec->ppmstab) {
512				/* Convert the PPM marker segment data into a collection of streams
513				  (one stream per tile-part). */
514				if (!(dec->pkthdrstreams = jpc_ppmstabtostreams(dec->ppmstab))) {
515					abort();
516				}
517				jpc_ppxstab_destroy(dec->ppmstab);
518				dec->ppmstab = 0;
519			}


Actual results:

crash

Expected results:

crash

Additional info:


Credits:

This vulnerability is detected by team OWL337, with our custom fuzzer collAFL. Please contact ganshuitao@gmail.com   and chaoz@tsinghua.edu.cn if you need more info about the team, the tool or the vulnerability.

Comment 2 Josef Ridky 2017-08-25 10:37:07 UTC
Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution. 

For information on how to contact the Red Hat production support team, please visit:
    https://www.redhat.com/support/process/production/#howto

For proper identification of issue are required properly filled following information:

- Description of problem
- Version-Release number of selected component (if applicable)
- Steps to Reproduce
- Actual results
- Expected results
- Additional info

Comment 3 Josef Ridky 2019-06-28 07:22:32 UTC
Due no reaction from Red Hat Security team and no CVE assigned, I am closing this as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.