When binding against a DN during authentication, the reply from 389-ds-base will be different whether the DN exists or not. This can be used by an unauthenticated attacker to check the existence of an entry in the LDAP database.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=1905565 | issue tracking patch vendor advisory |
| https://github.com/389ds/389-ds-base/issues/4480 | third party advisory patch |
| https://github.com/389ds/389-ds-base/commit/cc0f69283abc082488824702dae485b8eae938bc | third party advisory patch |
| https://github.com/389ds/389-ds-base/commit/b6aae4d8e7c8a6ddd21646f94fef1bf7f22c3f32 | third party advisory patch |