Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activati...
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| Debian:13 | tomcat11 |
Toutes les versions |
— |
| Debian:14 | tomcat11 |
Toutes les versions |
— |
| Debian:12 | tomcat10 |
Toutes les versions |
— |
| Debian:13 | tomcat10 |
Toutes les versions |
— |
| Debian:14 | tomcat10 |
Toutes les versions |
— |
| Debian:12 | tomcat9 |
< 9.0.70-2 |
9.0.70-2 |
| Debian:13 | tomcat9 |
< 9.0.70-2 |
9.0.70-2 |
| Debian:14 | tomcat9 |
< 9.0.70-2 |
9.0.70-2 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
Not Failing Securely ('Failing Open') vulnerability in Apache Tomcat. If the OpenSSLLifecycleListener is configured to use FIPS mode but FIPS activation fails, Tomcat logs and error but continues to use JSSE in non-FIPS mode with the provided configuration. This issue affects Apache Tomcat: from 11.0.0-M14 through 11.0.26, from 10.1.22 through 10.1.60, from 9.0.92 through 9.0.122. Users are recommended to upgrade to version 11.0.27, 10.1.61 or 9.0.123, which fix the issue.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Références
- advisory security-tracker.debian.org