Описание
ELSA-2026-26453: 389-ds-base security update (IMPORTANT)
[1.3.11.1-5.0.9]
- Security fix for CVE-2026-9064 [Orabug: 39570202]
[1.3.11.1-5.0.7]
- Security fix for CVE-2025-14905 [Orabug: 39146844]
[1.3.11.1-5.0.5]
- Allow Uniqueness plugin to search uniqueness attributes using custom matching rules [Orabug: 38388205]
Обновленные пакеты
Oracle Linux 7
Oracle Linux x86_64
389-ds-base
1.3.11.1-5.0.9.el7_9
389-ds-base-devel
1.3.11.1-5.0.9.el7_9
389-ds-base-libs
1.3.11.1-5.0.9.el7_9
389-ds-base-snmp
1.3.11.1-5.0.9.el7_9
Связанные CVE
Связанные уязвимости
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls within the default maximum BER message size (2 MB), causing excessive CPU consumption and heap allocation on the server. Under concurrent exploitation, this leads to significant latency degradation, worker thread starvation, or out-of-memory termination, resulting in a denial of service.
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls within the default maximum BER message size (2 MB), causing excessive CPU consumption and heap allocation on the server. Under concurrent exploitation, this leads to significant latency degradation, worker thread starvation, or out-of-memory termination, resulting in a denial of service.
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() function in the LDAP server does not enforce an upper bound on the number of controls per LDAP message. A remote, unauthenticated attacker can send a specially crafted LDAP request containing hundreds of thousands of minimal controls within the default maximum BER message size (2 MB), causing excessive CPU consumption and heap allocation on the server. Under concurrent exploitation, this leads to significant latency degradation, worker thread starvation, or out-of-memory termination, resulting in a denial of service.
A flaw was found in 389-ds-base. The get_ldapmessage_controls_ext() fu ...
