UBUNTU-CVE-2024-6119: High severity ubuntu/nodejs vulnerability
Issue summary: 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. Impact summary: 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/opensslto a version that resolves this vulnerability.Fixed in 3.0.2-0ubuntu1.18 - Upgrade
Upgrade
ubuntu/opensslto a version that resolves this vulnerability.Fixed in 3.0.2-0ubuntu1.18+Fips1 - Upgrade
Upgrade
ubuntu/edk2to a version that resolves this vulnerability.Fixed in 2024.02-2ubuntu0.6 - Upgrade
Upgrade
ubuntu/opensslto a version that resolves this vulnerability.Fixed in 3.0.13-0ubuntu3.4 - Upgrade
Upgrade
ubuntu/openssl-fipsto a version that resolves this vulnerability.Fixed in 3.0.13-0ubuntu3.6+Fips1
Event History
Frequently Asked Questions
Which deployments are most likely to be exposed?
Applications acting as TLS clients or otherwise performing certificate name checks are the primary concern. TLS servers are generally not affected because they rarely request client certificates and typically do not check a presented client certificate against a reference identity.
What must an attacker provide to trigger the denial of service?
The application must perform a name check against an expected DNS name, email address, or IP address, and compare it with an otherName subject alternative name in an X.509 certificate. Basic certificate-chain validation alone is not affected.