Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMiroslav Hradílek
2018-11-20 11:54:02 UTC
Description of problem:
Previously netpbm-progs used linked jasper library from the system which is watched for security. Current rhel-8 version uses built in implementation containing security flaws.
This was fortunately revealed by failing
/CoreOS/netpbm/Security/CVE-2011-4516-CVE-2011-4517-jasper-heap-buffer-overflow-flaws
Version-Release number of selected component (if applicable):
netpbm-10.82.00-4.el8.x86_64
netpbm-progs-10.82.00-4.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. ldd /usr/bin/jpeg2ktopam
^ This might affect other inaries from the package.
Actual results:
linux-vdso.so.1 (0x00007fff669cc000)
libnetpbm.so.11 => /lib64/libnetpbm.so.11 (0x00007f9bf18d3000)
libm.so.6 => /lib64/libm.so.6 (0x00007f9bf1551000)
libc.so.6 => /lib64/libc.so.6 (0x00007f9bf118d000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9bf1d52000)
Expected results:
use shared libjasper.so
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=747726#c33
AFAICS, we regressed from using system to bundled jasper via the following change in Fedora:
https://src.fedoraproject.org/cgit/rpms/netpbm.git/commit/?id=9ec28379f3b97ef8b8c3922919dcd29d70c93e7a
That's a rebase of netpbm to version 10.75.99. There's no mention in the commit to explain why we stopped using system jasper.
However, I see that we rebased netpbm to version 10.79.00 (i.e. newer than the one in the above Fedora commit) in Red Hat Enterprise Linux 7.5, while still keeping the use of system jasper. That makes me assume there's either no hard requirement to use bundled jasper 10.75.99 and later, or that if there was a reason, it disappeared until 10.79.00. Fedora has also been using jasper 1.900.1 until late 2016, so newer system jasper can not be a reason for the above change done in mid-2016.