RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1485272 - There is a reachable assertion abort in function JPC_NOMINALGAIN() of JasPer that will lead to remote denial of service attack.
Summary: There is a reachable assertion abort in function JPC_NOMINALGAIN() of JasPer ...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: jasper
Version: 7.5-Alt
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Josef Ridky
QA Contact: Desktop QE
Depends On:
TreeView+ depends on / blocked
Reported: 2017-08-25 09:08 UTC by owl337
Modified: 2019-06-28 07:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-28 07:22:20 UTC
Target Upstream Version:

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

Description owl337 2017-08-25 09:08:49 UTC
Created attachment 1318057 [details]
Triggered by  "./imginfo -f POC1"

Description of problem:

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

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

<= latest verison

How reproducible:

./imginfo -f POC1

Steps to Reproduce:

The output information is as follows:

$ ./imginfo -f POC1
imginfo: /home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c:144: int JPC_NOMINALGAIN(int, int, int, int): Assertion `qmfbid == JPC_COX_RFT' failed.
Aborted (core dumped)

The gdb debugging information is listed below:
(gdb) set args POC1
(gdb) r 
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/icy/secreal/jasper/install/bin/imginfo -f  fuzz/output/crashes/id\:000001\,sig\:06\,src\:000004\,op\:flip1\,pos\:101

Breakpoint 1, JPC_NOMINALGAIN (qmfbid=129, numlvls=0, lvlno=0, orient=0)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c:144
144		assert(qmfbid == JPC_COX_RFT);
(gdb) n
imginfo: /home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c:144: int JPC_NOMINALGAIN(int, int, int, int): Assertion `qmfbid == JPC_COX_RFT' failed.

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) bt 
#0  0x00007ffff71f8428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1  0x00007ffff71fa02a in __GI_abort () at abort.c:89
li#2  0x00007ffff71f0bd7 in __assert_fail_base (fmt=<optimized out>, 
    assertion=assertion@entry=0x7ffff7bc1c8d "qmfbid == JPC_COX_RFT", 
    file=file@entry=0x7ffff7bc1c40 "/home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c", 
    line=line@entry=144, function=function@entry=0x7ffff7bc1ca3 "int JPC_NOMINALGAIN(int, int, int, int)")
    at assert.c:92
#3  0x00007ffff71f0c82 in __GI___assert_fail (assertion=0x7ffff7bc1c8d "qmfbid == JPC_COX_RFT", 
    file=0x7ffff7bc1c40 "/home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c", line=144, 
    function=0x7ffff7bc1ca3 "int JPC_NOMINALGAIN(int, int, int, int)") at assert.c:101
#4  0x00007ffff7b81f45 in JPC_NOMINALGAIN (qmfbid=129, numlvls=0, lvlno=0, orient=0)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c:144st
#5  0x00007ffff7b43066 in jpc_dec_tileinit (dec=<optimized out>, tile=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:818
#6  jpc_dec_process_sod (dec=<optimized out>, ms=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:593
#7  0x00007ffff7b49ceb in jpc_dec_decode (dec=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:424
#8  jpc_decode (in=<optimized out>, optstr=<optimized out>)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_dec.c:261
---Type <return> to continue, or q <return> to quit---
#9  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
#10 0x0000000000401bab in main (argc=<optimized out>, argv=<optimized out>)
    at /home/icy/secreal/jasper/src/appl/imginfo.c:238

Trigged in:
JPC_NOMINALGAIN (qmfbid=129, numlvls=0, lvlno=0, orient=0)
    at /home/icy/secreal/jasper/src/libjasper/jpc/jpc_t1cod.c:144
139		numlvls = 0;
141		if (qmfbid == JPC_COX_INS) {
142			return 0;
143		}
144		assert(qmfbid == JPC_COX_RFT);
145		if (lvlno == 0) {
146			assert(orient == JPC_TSFB_LL);
147			return 0;
148		} else {

Actual results:


Expected results:


Additional info:


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

Comment 2 Josef Ridky 2017-08-25 10:37:02 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:

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 Agostino Sarubbo 2017-08-29 10:18:57 UTC
Dear owl337, I don't know if you are requesting cve by yourself, but the requested CVEs about jasper are just DUPLICATES.

Before request a CVE please check if the issue already exist on the upstream bugtracker: https://github.com/mdadams/jasper/issues/50

Comment 4 owl337 2017-08-29 14:03:33 UTC

At first, I am very sorry to hear that. I have checked all the bugs of this year. Maybe vendor should fix the bugs exposed some months ago. It's hard to make sure this bug will be duplicated with the bug reported at last year.

Thanks for your remind. I will report the new bugs of jasper to upstream bugtracker in future.

Comment 5 Agostino Sarubbo 2017-08-29 14:09:19 UTC
For all issues you find I'd suggest:

1) Check if exist in upstream bugtracker
2) Check if exist here: https://nvd.nist.gov/vuln/search?search_type=last3months&cves=on
3) Check here: https://marc.info/?l=oss-security
4) Check here: https://marc.info/?l=full-disclosure
5) Contact upstream maintainer

Comment 6 Josef Ridky 2019-06-28 07:22:20 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.