Information Exposure Affecting 389-ds-base-snmp package, versions <0:1.4.3.8-7.module+el8.3.0+10310+6e88d919
Threat Intelligence
EPSS
0.11% (46th
percentile)
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-389DSBASESNMP-2092120
- published 26 Jul 2021
- disclosed 7 Dec 2020
Introduced: 7 Dec 2020
CVE-2020-35518 Open this link in a new tabHow to fix?
Upgrade Centos:8 389-ds-base-snmp to version 0:1.4.3.8-7.module+el8.3.0+10310+6e88d919 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream 389-ds-base-snmp package and not the 389-ds-base-snmp package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
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.
References
- https://access.redhat.com/security/cve/CVE-2020-35518
- https://bugzilla.redhat.com/show_bug.cgi?id=1905565
- https://github.com/389ds/389-ds-base/commit/b6aae4d8e7c8a6ddd21646f94fef1bf7f22c3f32
- https://github.com/389ds/389-ds-base/commit/cc0f69283abc082488824702dae485b8eae938bc
- https://github.com/389ds/389-ds-base/issues/4480
- https://access.redhat.com/errata/RHSA-2021:1086
CVSS Scores
version 3.1