CVE-2014-0400
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnspecified vulnerability in the Oracle Internet Directory component in Oracle Fusion Middleware 11.1.1.6 and 11.1.1.7 allows remote authenticated users to affect confidentiality via vectors related to OID LDAP server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOracle Internet Directory (OID) 11.1.1.6 and 11.1.1.7 contains an unspecified vulnerability in the OID LDAP server component that allows remote authenticated attackers to access sensitive information, compromising confidentiality. The vulnerability requires authentication but can be exploited remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 11.1.1.6.0= 11.1.1.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:M/Au:S/C:C/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Oracle Internet Directory versionQuery the OID LDAP server for its version using an LDAP tool (e.g., ldapsearch) against the root DSE, or check the Oracle Inventory via 'opatch lsinventory' looking for Oracle Internet Directory component versionAffected if The installed version equals 11.1.1.6.0 or 11.1.1.7.0
-
Verify OID LDAP server process is runningCheck for oidldapd or oidmon processes on the server (e.g., 'ps -ef | grep oid') or check Oracle Enterprise Manager for OID component statusAffected if The OID LDAP server process is running and the version is 11.1.1.6.0 or 11.1.1.7.0
-
Confirm LDAP port exposureCheck if the LDAP port (typically 3060 for OID) is listening on a network interface accessible to remote systems (e.g., 'netstat -an | grep 3060' or review firewall rules)Affected if The OID LDAP port is exposed to untrusted networks and the version is 11.1.1.6.0 or 11.1.1.7.0
-
Check authentication configurationReview OID authentication settings via Oracle Enterprise Manager or by querying cn=oraclecontext, cn=OID server configuration entries to determine if anonymous or low-privilege remote authentication is permittedAffected if Remote authentication is enabled and the version is 11.1.1.6.0 or 11.1.1.7.0
A user is affected if Oracle Internet Directory version 11.1.1.6.0 or 11.1.1.7.0 is installed with the OID LDAP server running and accessible to remote attackers who can authenticate.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Oracle Critical Patch Update (CPU) January 2014 or later which addresses CVE-2014-0400, or upgrade to Oracle Internet Directory version 11.1.1.9 or higher where the vulnerability has been remediated.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0400 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data