Описание
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher.
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2015-3230
- https://access.redhat.com/errata/RHBA-2015:1554
- https://access.redhat.com/security/cve/CVE-2015-3230
- https://bugzilla.redhat.com/show_bug.cgi?id=1230996
- https://bugzilla.redhat.com/show_bug.cgi?id=1232096
- https://fedorahosted.org/389/ticket/48194
- http://directory.fedoraproject.org/docs/389ds/releases/release-1-3-3-12.html
- http://lists.fedoraproject.org/pipermail/package-announce/2015-October/168985.html
EPSS
CVE ID
Связанные уязвимости
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher.
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher.
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.12 does not enforce the nsSSL3Ciphers preference when creating an sslSocket, which allows remote attackers to have unspecified impact by requesting to use a disabled cipher.
389 Directory Server (formerly Fedora Directory Server) before 1.3.3.1 ...
EPSS