Skip to content
Noroxi
CVE-2017-15135· NVD / CVE Program· CNA redhat

It was found that 389-ds-base since 1.3.6.1 up to and including 1.4.0.3 did not always handle internal hash comparison operations correctly

It was found that 389-ds-base since 1.3.6.1 up to and including 1.4.0.3 did not always handle internal hash comparison operations correctly during the authentication process. A remote, unauthenticated attacker could potentially use this flaw to bypass the authentication process under very rare and specific circumstances.

HighCVSS 8.1 · v3.0—No exploit Fix available
Published
Jan 24, 2018
Updated
Jun 16, 2026
EPSS
3.8% · 90th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.8%

Affected systems

VendorProduct
fedoraproject389 directory server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject 389 directory server1.3.6.1 and later · up to 1.4.0.3 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat, Inc. 389-ds-base

    • since 1.3.6.1 up to and including 1.4.0.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12389-ds-basebefore 1.3.7.9-11.3.7.9-1
openSUSE:Leap 15.0389-dsbefore 1.4.0.3-lp150.3.3.11.4.0.3-lp150.3.3.1
Red Hat:enterprise_linux:6::client389-ds-basebefore 0:1.2.11.15-94.el6_90:1.2.11.15-94.el6_9
Red Hat:enterprise_linux:6::client389-ds-base-debuginfobefore 0:1.2.11.15-94.el6_90:1.2.11.15-94.el6_9
Red Hat:enterprise_linux:6::client389-ds-base-develbefore 0:1.2.11.15-94.el6_90:1.2.11.15-94.el6_9
Red Hat:enterprise_linux:6::client389-ds-base-libsbefore 0:1.2.11.15-94.el6_90:1.2.11.15-94.el6_9
Red Hat:enterprise_linux:7::client389-ds-basebefore 0:1.3.6.1-28.el7_40:1.3.6.1-28.el7_4
Red Hat:enterprise_linux:7::client389-ds-base-debuginfobefore 0:1.3.6.1-28.el7_40:1.3.6.1-28.el7_4
Red Hat:enterprise_linux:7::client389-ds-base-develbefore 0:1.3.6.1-28.el7_40:1.3.6.1-28.el7_4
Red Hat:enterprise_linux:7::client389-ds-base-libsbefore 0:1.3.6.1-28.el7_40:1.3.6.1-28.el7_4
Red Hat:enterprise_linux:7::client389-ds-base-snmpbefore 0:1.3.6.1-28.el7_40:1.3.6.1-28.el7_4
SUSE:Linux Enterprise Module for Server Applications 15389-dsbefore 1.4.0.3-4.7.521.4.0.3-4.7.52

Other highest-scoring records for the same primary product.

  • CVE-2017-7551389-ds-base version before 1.3.5.19 and 1.3.6.7 are vulnerable to password brute-force attacks during account lockout due to different retur
    39Monitor
  • CVE-2019-3883In 389-ds-base up to version 1.4.1.2, requests are handled by workers threads.
    32Monitor
  • CVE-2018-14648A flaw was found in 389 Directory Server.
    32Monitor
  • CVE-2018-14638A flaw was found in 389-ds-base before version 1.3.8.4-13.
    31Monitor
  • CVE-2018-14624A vulnerability was discovered in 389-ds-base through versions 1.3.7.10, 1.3.8.8 and 1.4.0.16.
    31Monitor
  • CVE-2018-1089389-ds-base before versions 1.4.0.9, 1.3.8.1, 1.3.6.15 did not properly handle long search filters with characters needing escapes, possibly
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:389-ds-base1.3.7.9-1 · Debian:12Package registry (OSV)
opensuse:389-ds1.4.0.3-lp150.3.3.1 · openSUSE:Leap 15.0Package registry (OSV)
red hat:389-ds-base0:1.3.6.1-28.el7_4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:389-ds-base-debuginfo0:1.3.6.1-28.el7_4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:389-ds-base-devel0:1.3.6.1-28.el7_4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:389-ds-base-libs0:1.3.6.1-28.el7_4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:389-ds-base-snmp0:1.3.6.1-28.el7_4 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:389-ds1.4.0.3-4.7.52 · SUSE:Linux Enterprise Module for Server Applications 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records