The SASL authentication functionality in 389 Directory Server before 1.2.11.26 allows remote authenticated users to connect as an arbitrary
The SASL authentication functionality in 389 Directory Server before 1.2.11.26 allows remote authenticated users to connect as an arbitrary user and gain privileges via the authzid parameter in a SASL/GSSAPI bind.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; 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- Published
- Mar 18, 2014
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 82th percentile
- CWE
- CWE-287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| fedoraproject | 389 directory server | cpe:2.3:a:fedoraproject:389_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 serverup to 1.2.11.25 inclusive
- fedoraproject 389 directory server1.2.11.1
- fedoraproject 389 directory server1.2.11.10
- fedoraproject 389 directory server1.2.11.11
- fedoraproject 389 directory server1.2.11.12
- fedoraproject 389 directory server1.2.11.13
- fedoraproject 389 directory server1.2.11.14
- fedoraproject 389 directory server1.2.11.15
- fedoraproject 389 directory server1.2.11.17
- fedoraproject 389 directory server1.2.11.19
- fedoraproject 389 directory server1.2.11.20
- fedoraproject 389 directory server1.2.11.21
- fedoraproject 389 directory server1.2.11.22
- fedoraproject 389 directory server1.2.11.23
- fedoraproject 389 directory server1.2.11.5
- fedoraproject 389 directory server1.2.11.6
- fedoraproject 389 directory server1.2.11.8
- fedoraproject 389 directory server1.2.11.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | 389-ds-base | before 1.3.2.9-1.1 | 1.3.2.9-1.1 |
| Red Hat:enterprise_linux:6::client | 389-ds-base | before 0:1.2.11.15-32.el6_5 | 0:1.2.11.15-32.el6_5 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-debuginfo | before 0:1.2.11.15-32.el6_5 | 0:1.2.11.15-32.el6_5 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-devel | before 0:1.2.11.15-32.el6_5 | 0:1.2.11.15-32.el6_5 |
| Red Hat:enterprise_linux:6::client | 389-ds-base-libs | before 0:1.2.11.15-32.el6_5 | 0:1.2.11.15-32.el6_5 |
Same product
fedoraproject: all recordsOther 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 retur39Monitor
- CVE-2017-15135It 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 33Monitor
- 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
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:389-ds-base | 1.3.2.9-1.1 · Debian:12 | Package registry (OSV) |
| red hat:389-ds-base | 0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-debuginfo | 0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-devel | 0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:389-ds-base-libs | 0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::client | Package 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.
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.
Credits
All researchersFinders, 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
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- rhn.redhat.com/errata/RHSA-2014-0292.html
- secunia.com/advisories/57412
- secunia.com/advisories/57427
- fedorahosted.org/389/ticket/47739
Vendor advisories and official records. Exploit/PoC links are deliberately left out.