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 1652599 - CVE-2018-20533 libsolv: NULL pointer dereference in function testcase_str2dep_complex [rhel-8]
Summary: CVE-2018-20533 libsolv: NULL pointer dereference in function testcase_str2dep...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libsolv
Version: 8.1
Hardware: All
OS: All
high
urgent
Target Milestone: rc
: 8.0
Assignee: Jaroslav Rohel
QA Contact: Karel Srot
URL:
Whiteboard:
: 1669577 (view as bug list)
Depends On:
Blocks: CVE-2018-20533
TreeView+ depends on / blocked
 
Reported: 2018-11-22 13:06 UTC by shuitao gan
Modified: 2019-06-14 00:48 UTC (History)
4 users (show)

Fixed In Version: libsolv-0.6.35-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 00:48:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Triggered by “./testsolv POC0” (15.01 KB, application/octet-stream)
2018-11-22 13:06 UTC, shuitao gan
no flags Details

Description shuitao gan 2018-11-22 13:06:53 UTC
Created attachment 1507932 [details]
Triggered by “./testsolv POC0”

version: libsolv2.4
Summary: 

There is an illegal address access at ext/testcase.c:577 testcase_str2dep_complex in libsolv.

Description:

The asan debug is as follows:

$./testsolv POC0

=================================================================
==37349==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x7fab0e11bf2b bp 0x7ffdfc044b70 sp 0x7ffdfc044a90 T0)
    #0 0x7fab0e11bf2a in testcase_str2dep_complex /home/company/real_sanitize/libsolv-master/ext/testcase.c:577
    #1 0x7fab0e11c80f in testcase_str2dep /home/company/real_sanitize/libsolv-master/ext/testcase.c:656
    #2 0x7fab0e12e64a in testcase_read /home/company/real_sanitize/libsolv-master/ext/testcase.c:2952
    #3 0x402aa5 in main /home/company/real_sanitize/libsolv-master/tools/testsolv.c:148
    #4 0x7fab0d9d2a3f in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x20a3f)
    #5 0x401bb8 in _start (/home/company/real_sanitize/libsolv-master/build/install/bin/testsolv+0x401bb8)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /home/company/real_sanitize/libsolv-master/ext/testcase.c:577 testcase_str2dep_complex
==37349==ABORTING

Comment 2 Jaroslav Rohel 2018-12-05 13:20:59 UTC
Please, which version of libsolv do you have? The "libsolv2.4" seems strange.
In RHEL 8 is "libsolv-0.6.35".

Comment 3 Jaroslav Rohel 2018-12-11 13:08:04 UTC
PR https://github.com/openSUSE/libsolv/pull/291

Comment 6 Riccardo Schirone 2019-03-12 14:21:08 UTC
*** Bug 1669577 has been marked as a duplicate of this bug. ***


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