Enterprise Linux DesktopOperating system · Redhat
CVE-2017-2668
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited389-ds-base before versions 1.3.5.17 and 1.3.6.10 is vulnerable to an invalid pointer dereference in the way LDAP bind requests are handled. A remote unauthenticated attacker could use this flaw to make ns-slapd crash via a specially crafted LDAP bind request, resulting in denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence389-ds-base contains an invalid pointer dereference vulnerability in its LDAP bind request handling code. A remote unauthenticated attacker can send a specially crafted LDAP bind request that triggers the invalid pointer dereference, causing the ns-slapd process to crash and resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise Linux DesktopOperating system
= 6.0= 7.0
Enterprise Linux ServerOperating system
= 6.0= 7.0
Enterprise Linux WorkstationOperating system
= 6.0= 7.0>= 1.3.5.0, < 1.3.5.17>= 1.3.6.0, < 1.3.6.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if 389-ds-base is installedRun 'rpm -qa | grep 389-ds-base' on Red Hat/Fedora systems, or check package list on your systemAffected if The package is not installed, the system is not affected by this vulnerability
-
Determine installed version of 389-ds-baseRun 'rpm -q 389-ds-base' to get the exact version number installedAffected if Version is 1.3.5.0 through 1.3.5.16, or 1.3.6.0 through 1.3.6.9, or matches RHEL 6.0/7.0 versions - compare your version to these affected ranges
-
Verify ns-slapd process is runningRun 'ps aux | grep ns-slapd' or 'systemctl status dirsrv' to check if the directory server is activeAffected if The service is not running, the DoS cannot be triggered against your environment
-
Confirm LDAP bind is enabled (default)Check server configuration via 'ldapsearch -x -h localhost -p 389 -s base bindPolicy' or review cn=config in the directoryAffected if LDAP bind is disabled, the attack surface is reduced but the vulnerable code path may still exist
Your environment is affected if 389-ds-base is installed with a version in the ranges 1.3.5.0-1.3.5.16 or 1.3.6.0-1.3.6.9 (or matching RHEL 6.0/7.0), the ns-slapd process is running, and LDAP bind requests are accepted (default configuration).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.3.5.171.3.6.10
Upgrade 389-ds-base to version 1.3.5.17 or later in the 1.3.5.x branch, or version 1.3.6.10 or later in the 1.3.6.x branch. Apply during a planned maintenance window.
Fix this in Enterprise Linux Desktop
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-2668 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data