First published: Wed Feb 19 2025(Updated: )
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 | Affected Version | How to fix |
---|---|---|
F5 BIG-IP Next (LTM, WAF) | >=20.2.0<=20.3.0 | |
F5 BIG-IP Next | >=1.7.0<=1.9.2 | |
F5 BIG-IP Next | >=1.1.0<=1.4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of F5-K000149304 is considered critical due to the potential for application termination and denial of service.
To fix F5-K000149304, you should update to the latest software version that has addressed the vulnerability.
F5-K000149304 affects F5 BIG-IP Next (LTM), F5 BIG-IP Next SPK, and F5 BIG-IP Next CNF within specified version ranges.
The impact of F5-K000149304 includes abnormal application termination that can lead to denial of service.
There are no recommended workarounds for F5-K000149304; applying the appropriate updates is necessary.