Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2014-0132: The SASL authentication functionality in 389 Directory Server before 1.2.11.26 allows remote authenticated users to connect as an arbitrary…

MediumCVSS 6.5 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 82.7% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: 389-ds-base (Debian:12) 1.3.2.9-1.1; 389-ds-base (Red Hat:enterprise_linux:6::client) 0:1.2.11.15-32.el6_5; 389-ds-base-debuginfo (Red Hat:enterprise_linux:6::client) 0:1.2.11.15-32.el6_5.

Low priority for now. Upgrade to 389-ds-base (Debian:12) 1.3.2.9-1.1; 389-ds-base (Red Hat:enterprise_linux:6::client) 0:1.2.11.15-32.el6_5; 389-ds-base-debuginfo (Red Hat:enterprise_linux:6::client) 0:1.2.11.15-32.el6_5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Mar 18, 2014
Updated
Jun 16, 2026
EPSS
2.1% · 82th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2014-0132

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

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 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

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.2.9-1.11.3.2.9-1.1
Red Hat:enterprise_linux:6::client389-ds-basebefore 0:1.2.11.15-32.el6_50:1.2.11.15-32.el6_5
Red Hat:enterprise_linux:6::client389-ds-base-debuginfobefore 0:1.2.11.15-32.el6_50:1.2.11.15-32.el6_5
Red Hat:enterprise_linux:6::client389-ds-base-develbefore 0:1.2.11.15-32.el6_50:1.2.11.15-32.el6_5
Red Hat:enterprise_linux:6::client389-ds-base-libsbefore 0:1.2.11.15-32.el6_50:1.2.11.15-32.el6_5

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…
    39Monitor
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2013-2219Jul 31, 2013 · The Red Hat Directory Server before 8.2.11-13 and 389 Directory Server do not properly restrict access to entity attributes, which allows…
    17Monitor
  • ← EarlierCVE-2013-4283Sep 10, 2013 · ns-slapd in 389 Directory Server before 1.3.0.8 allows remote attackers to cause a denial of service (server crash) via a crafted…
    21Monitor
  • Later →CVE-2014-3562Aug 21, 2014 · Red Hat Directory Server 8 and 389 Directory Server, when debugging is enabled, allows remote attackers to obtain sensitive replicated…
    21Monitor

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.2.9-1.1 · Debian:12Package registry (OSV)
red hat:389-ds-base0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-debuginfo0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-devel0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:389-ds-base-libs0:1.2.11.15-32.el6_5 · Red Hat:enterprise_linux:6::clientPackage 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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

CVSS 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.

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);

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records