CVE-2014-3999 json
The Horde_Ldap library before 2.0.6 for Horde allows remote attackers to bypass authentication by leveraging knowledge of the LDAP bind use…
published 8y ago modified 4mo ago also EUVD-2014-3930
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
The Horde_Ldap library before 2.0.6 for Horde allows remote attackers to bypass authentication by leveraging knowledge of the LDAP bind user DN.
Patch / fix
Is CVE-2014-3999 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-3999 updated cvss 5.0
php-horde-Horde-Ldap: connect to LDAP without knowing the password
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.42% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/horde/horde/commit/4c3e18f1724ab39bfef10c189a5b52036a744d55
patch
-
openwall.com
/lists/oss-security/2014/06/14/1
mailing-list
-
bugzilla.redhat.com
/show_bug.cgi?id=1109628
issue-tracking
-
securityfocus.com
/bid/68014
vdb-entry, third-party-advisory
-
marc.info
/?l=horde-announce&m=140178644816474&w=2
mailing-list
Sources
- CVE List CVE-2014-3999
- NVD CVE-2014-3999
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.