Bug 2306158 (CVE-2024-6119)

Summary: CVE-2024-6119 openssl: Possible denial of service in X.509 name checks
Product: [Other] Security Response Reporter: Patrick Del Bello <pdelbell>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: akostadi, amasferr, asdas, bmontgom, cbartlet, chazlett, csutherl, dbosanac, dmayorov, doconnor, dpaolell, eparis, jburrell, jcantril, jclere, jdelft, jlledo, jreimann, jupierce, lgarciaa, mbenatto, mbiarnes, mdessi, mjaros, mkudlej, mlewando, mmakovy, mrezanin, mrizzi, nstielau, nyancey, pcattana, pjanda, pjindal, pjones, plodge, raravind, security-response-team, sidsharm, sponnaga, szappis, talessio, teagle, tjochec, vlaad, ximhan, yuxzhu
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in OpenSSL. Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Deadline: 2024-09-04   

Description Patrick Del Bello 2024-08-20 17:55:58 UTC
Abnormal termination of an application can a cause a denial of
service.

Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an otherName subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.

Note that basic certificate chain validation (signatures, dates, ...) is not
affected, the denial of service can occur only when the application also
specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they
generally don't perform a name check against a "reference identifier" (expected
identity), but rather extract the presented identity after checking the
certificate chain. So TLS servers are generally not affected and the severity
of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
OpenSSL 1.1.1 and 1.0.2 are also not affected by this issue.

OpenSSL 3.3, 3.2, 3.1 and 3.0 are vulnerable to this issue.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.2

OpenSSL 3.2 users should upgrade to OpenSSL 3.2.3

OpenSSL 3.1 users should upgrade to OpenSSL 3.1.7

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.15

Comment 1 errata-xmlrpc 2024-09-18 18:43:30 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:6783 https://access.redhat.com/errata/RHSA-2024:6783

Comment 5 errata-xmlrpc 2024-10-09 05:32:38 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.16

Via RHSA-2024:7599 https://access.redhat.com/errata/RHSA-2024:7599

Comment 9 errata-xmlrpc 2024-11-06 12:01:17 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:8935 https://access.redhat.com/errata/RHSA-2024:8935

Comment 11 errata-xmlrpc 2024-12-11 01:09:48 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.17

Via RHSA-2024:10818 https://access.redhat.com/errata/RHSA-2024:10818