CVE-2017-2668
Last modified
CVE-2017-2668 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. 389-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.. EPSS estimates a 2.63% chance of exploitation in the next 30 days.
Description
389-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.
Metrics
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Fedoraproject | 389 Directory Server | >= 1.3.5.0, < 1.3.5.17 |
| Fedoraproject | 389 Directory Server | >= 1.3.6.0, < 1.3.6.10 |
| Redhat | Enterprise Linux Desktop | 6.0 |
| Redhat | Enterprise Linux Desktop | 7.0 |
| Redhat | Enterprise Linux Server | 6.0 |
| Redhat | Enterprise Linux Server | 7.0 |
| Redhat | Enterprise Linux Workstation | 6.0 |
| Redhat | Enterprise Linux Workstation | 7.0 |
References
- http://www.securityfocus.com/bid/97524Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:0893Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:0920Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2668Issue Tracking, Third Party Advisory
- https://pagure.io/389-ds-base/issue/49220Issue Tracking, Third Party Advisory
- http://www.securityfocus.com/bid/97524Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:0893Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:0920Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2668Issue Tracking, Third Party Advisory
- https://pagure.io/389-ds-base/issue/49220Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2668?
How severe is CVE-2017-2668?
How do I fix CVE-2017-2668?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2662A flaw was found in Foreman's katello plugin version 3.4.5. …4.3
- CVE-2017-2663It was found that subscription-manager's DBus interface befo…8.2
- CVE-2017-2664CloudForms Management Engine (cfme) before 5.7.3 and 5.8.x b…6.5
- CVE-2017-2665The skyring-setup command creates random password for mongod…4.8
- CVE-2017-2666It was discovered in Undertow that the code that parsed the …6.5
- CVE-2017-2667Hammer CLI, a CLI utility for Foreman, before version 0.10.0…8.1
- CVE-2017-2669Dovecot before version 2.2.29 is vulnerable to a denial of s…3.7
- CVE-2017-2670It was found in Undertow before 1.3.28 that with non-clean T…7.5
- CVE-2017-2671The ping_unhash function in net/ipv4/ping.c in the Linux ker…
- CVE-2017-2672A flaw was found in foreman before version 1.15 in the loggi…6.5
- CVE-2017-2673An authorization-check flaw was discovered in federation con…6.8
- CVE-2017-2674JBoss BRMS 6 and BPM Suite 6 before 6.4.3 are vulnerable to …6.1
Are you affected by CVE-2017-2668?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
