CVE-2017-15134
What it is
A stack buffer overflow flaw was found in the way 389-ds-base 1.3.6.x before 1.3.6.13, 1.3.7.x before 1.3.7.9, 1.4.x before 1.4.0.5 handled certain LDAP search filters. A remote, unauthenticated attacker could potentially use this flaw to make ns-slapd crash via a specially crafted LDAP request, thus resulting in denial of service.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 3.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.9% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.9% · EPSS, next 30 days
- Weakness
- CWE-120 · Classic buffer overflow
- Record status
- Modified
Affected
- Fedoraproject 389 Directory Server < 1.3.6.13
- Fedoraproject 389 Directory Server < 1.3.7.9
- Fedoraproject 389 Directory Server < 1.4.0.5
- Redhat Enterprise Linux 7.4
- Redhat Enterprise Linux Desktop 7.0
- Redhat Enterprise Linux Server 7.0
- Redhat Enterprise Linux Server 7.4
- Redhat Enterprise Linux Workstation 7.0
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-15134.md and follow it. Check whether this project is affected by CVE-2017-15134. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://access.redhat.com/errata/RHSA-2018:0163
- https://bugzilla.redhat.com/show_bug.cgi?id=1531573
- https://pagure.io/389-ds-base/c/6aa2acdc3cad9
- https://access.redhat.com/errata/RHSA-2018:0163
- https://bugzilla.redhat.com/show_bug.cgi?id=1531573
- https://pagure.io/389-ds-base/c/6aa2acdc3cad9
References
- http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00033.html
- http://www.securityfocus.com/bid/102790
- https://access.redhat.com/errata/RHSA-2018:0163
- https://bugzilla.redhat.com/show_bug.cgi?id=1531573
- https://lists.debian.org/debian-lts-announce/2018/07/msg00018.html
- https://pagure.io/389-ds-base/c/6aa2acdc3cad9
- http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00033.html
- http://www.securityfocus.com/bid/102790
- https://access.redhat.com/errata/RHSA-2018:0163
- https://bugzilla.redhat.com/show_bug.cgi?id=1531573
- https://lists.debian.org/debian-lts-announce/2018/07/msg00018.html
- https://pagure.io/389-ds-base/c/6aa2acdc3cad9