389-ds-base: 389-ds-base: starttls plaintext-buffer retention allows on-path attacker to forge an ldap client's authentication result
- Published
- Last modified
- Status
- published
- Known exploitation
- Not listed in CISA KEV
- Public exploit
- None on Exploit-DB
- Exploitation: none
- Automatable: no
- Technical impact: total
?
Decision points from CISA's Vulnrichment, assessed (SSVC 2.0.3).
SSVC documentationSummary
A flaw was found in 389-ds-base. The server does not discard plaintext bytes already buffered from a client connection when negotiating StartTLS, allowing an on-path attacker to inject a crafted LDAP message that is processed after the TLS upgrade and whose response is delivered to the client in place of the client's own pending operation's response, due to messageID collision. This can cause a client application to treat a failed authentication (bind) attempt as successful.
Affected versions
- 389-ds-base
Version range not reported
- redhat-ds:11/389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- redhat-ds:12/389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- 389-ds:1.4/389-ds-base
Version range not reported
- 389-ds-base
Version range not reported
- 389-ds-base
Version range not reported