dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2010-2390

HIGH · 7.5 CVSS v2.0 Published 2010-10-14
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 Database Control component in EM Console in Oracle Database Server 10.1.0.5 and 10.2.0.3, Oracle Fusion Middleware 10.1.2.3 and 10.1.4.3, and Enterprise Manager Grid Control 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

Unspecified vulnerability in Oracle Enterprise Manager (EM) Console affecting Database Control component in Oracle Database Server 10.1.0.5/10.2.0.3, Fusion Middleware 10.1.2.3/10.1.4.3, and Enterprise Manager Grid Control. Exploitable remotely without authentication, allowing impact to confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Updates (CPU) for the relevant versions, disable or restrict network access to EM Console if not needed, or upgrade to patched Oracle versions. Oracle released patches for this issue in their July 2010 CPU.

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
Database ServerDatabase / datastore
Affected:= 10.1.0.5= 10.2.0.3
Fusion MiddlewareApplication
Affected:= 10.1.2.3= 10.1.4.3
Enterprise Manager Grid ControlApplication
Affected:all versions

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 Enterprise Manager Console is accessible
    Check if EM Console ports are listening. Database Control typically uses ports 1158, 5500, or 5501. Grid Control uses 4889, 4899, or 7200. Fusion Middleware EM uses 7777, 9700, or similar. Use 'netstat -an | grep -E "(1158|5500|5501|4889|4899|7200|7777|9700)"' or a port scanner to identify listening EM services.
    Affected if Any EM Console port is found listening and responding on the system
  2. Determine the EM component type
    Access the EM Console web interface (https://hostname:port/em) and check the console header or About page. Alternatively, check Oracle inventory files: $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml or look for directories like $ORACLE_HOME/db_1 (Database Control), $ORACLE_HOME/oms10g (Grid Control), or $ORACLE_HOME/EM_10g (Fusion Middleware).
    Affected if The component identifies as Database Control, Grid Control, or Fusion Middleware EM Console
  3. Verify the installed version of Database Control
    If using Database Control, check the version file: $ORACLE_HOME/db_1/sysman/config/bubbles.properties (contains version), or check the Oracle inventory: $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml. Run: 'cat $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml | grep -i "db_1"' to locate Database home and version.
    Affected if Version equals exactly 10.1.0.5 or 10.2.0.3
  4. Verify the installed version of Fusion Middleware EM
    Check the version in: $ORACLE_HOME/EM_10g/oc4j/j2ee/oc4j_web/webapps/em/WEB-INF/EMConfig.properties or check the Oracle Central Inventory. Run: 'cat $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml' to find Fusion Middleware home and version.
    Affected if Version equals exactly 10.1.2.3 or 10.1.4.3
  5. Verify if Enterprise Manager Grid Control is in use
    Check for Grid Control installation directories: $ORACLE_HOME/oms10g, $ORACLE_HOME/agent10g, or check Oracle inventory for homes with 'oms' or 'agent' designations. Access the Grid Control console and check the About page for version information.
    Affected if Grid Control is installed (any version, as all are affected per the CVE)

The environment is affected if any Oracle Enterprise Manager Console (Database Control, Fusion Middleware, or Grid Control) is running and the specific version matches one of the affected versions listed, or if Grid Control of any version is in use.

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 (CPU) for the relevant versions, disable or restrict network access to EM Console if not needed, or upgrade to patched Oracle versions. Oracle released patches for this issue in their July 2010 CPU.

Fix this in Database Server 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-2390 — 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-2390 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