dbcve.org
Fusion MiddlewareApplication · Oracle

CVE-2010-0853

HIGH · 7.5 CVSS v2.0 Published 2010-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the Oracle Internet Directory component in Oracle Database 9.2.0.8, 9.2.0.8, and DV; and Oracle Fusion Middleware 10.1.2.3 and 10.1.4.0.1; allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

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 · moderate confidence

Oracle Internet Directory contains an unspecified vulnerability allowing remote attackers to impact confidentiality, integrity, and availability. The vulnerability affects Oracle Database 9.2.0.8, 9.2.0.8 DV, and Oracle Fusion Middleware 10.1.2.3/10.1.4.0.1. Since the vectors are unknown, this appears to be a generic disclosure of a flaw in Oracle's LDAP directory service component.

MitigationApply Oracle Critical Patch Updates for 2010 or later; if these legacy Oracle versions remain in production, prioritize migration or isolation given the age of the vulnerability and unsupported status of affected releases.

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
Fusion MiddlewareApplication
Affected:= 10.1.2.3= 10.1.4.0.1
Database ServerDatabase / datastore
Affected:= 9.2.0.8= 9.2.0.8dv

CVSS 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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle Internet Directory is installed
    Check for Oracle Internet Directory processes or services. On Unix/Linux: ps -ef | grep -i oid or look for opmnctl processes. On Windows: check Services for 'Oracle Internet Directory' or look in Task Manager for oidldap or opmn processes.
    Affected if Oracle Internet Directory process or service is found running on the system
  2. Check Oracle Fusion Middleware version
    Locate the Fusion Middleware installation directory (typically ORACLE_HOME) and check the version. Look for an inventory file or run: $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml or check readme files in the OID directory. The OID component version should match 10.1.2.3 or 10.1.4.0.1.
    Affected if Oracle Fusion Middleware version is 10.1.2.3 or 10.1.4.0.1 with Oracle Internet Directory component present
  3. Check Oracle Database version
    If OID is using an embedded database, check the Oracle Database version by running: sqlplus / as sysdba then SELECT VERSION FROM V$INSTANCE; or check the oratab file and init.ora/spfile for version 9.2.0.8.
    Affected if Oracle Database version is 9.2.0.8 or 9.2.0.8 DV and is tied to Oracle Internet Directory
  4. Verify LDAP directory service is active
    Check if the OID LDAP service is listening on default ports (389, 636 for LDAP, or 4030-4035 for OID). Run: netstat -an | grep -E '389|636|4030|4031|4032' or use ldapsearch to test connectivity to the LDAP endpoint.
    Affected if LDAP ports are open and responding for Oracle Internet Directory on a system with the affected versions

The system is affected if Oracle Internet Directory is installed and the Oracle Fusion Middleware version is 10.1.2.3 or 10.1.4.0.1, or if Oracle Database version 9.2.0.8/9.2.0.8DV is present with the LDAP directory component running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates for 2010 or later; if these legacy Oracle versions remain in production, prioritize migration or isolation given the age of the vulnerability and unsupported status of affected releases.

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0853 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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