dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2007-5530

HIGH · 10.0 CVSS v2.0 Published 2007-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Oracle Database 10.1.0.5 and 10.2.0.3, and Enterprise Manager, has unknown impact and remote attack vectors, aka EM01.

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

Critical severity vulnerability in Oracle Database Enterprise Manager/Database Control web interface affecting versions 10.1.0.5 and 10.2.0.3. Despite 'unspecified' classification in the CVE description, the CVSS score of 10 indicates potential for complete system compromise through remote exploitation, likely enabling unauthenticated attacker to execute arbitrary code or gain administrative access to the Enterprise Manager console.

MitigationApply Oracle Critical Patch Update (CPU) from October 2007 that addresses EM01, or upgrade to a supported Oracle Database version since these affected releases are long-end-of-life. Restrict network access to Enterprise Manager ports as an interim compensating control.

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

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
Complete
Integrity
Complete
Availability
Complete

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

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 Oracle Database version
    Run 'sqlplus / as sysdba' and execute 'SELECT VERSION FROM V$INSTANCE;' or check 'lsnrctl status' output for version information
    Affected if Version displayed is exactly 10.1.0.5 or 10.2.0.3
  2. Determine if Enterprise Manager is configured
    Check if the Enterprise Manager repository exists by querying 'SELECT COUNT(*) FROM SYSMAN.MGMT_TARGETS;' in SQL*Plus, or look for EM-related processes running (emagent, emconsole)
    Affected if Enterprise Manager repository is present and EM processes are running
  3. Verify Database Control web interface status
    Check for EM console listener ports (commonly 1158, 5500, or 5520) using 'netstat -an | grep -E "1158|5500|5520"' or 'lsnrctl status' output
    Affected if Database Control console ports are listening and accessible over the network
  4. Confirm EM console accessibility
    Attempt to access the EM console URL 'https://hostname:port/em' (or HTTP) from a remote location, or verify the web service is exposed by reviewing listener.ora and sqlnet.ora configurations
    Affected if Enterprise Manager console is reachable without authentication or with default credentials
  5. Check Oracle October 2007 CPU applied status
    Query 'SELECT ACTION, VERSION FROM SYS.REGISTRY$HISTORY WHERE ACTION LIKE "%CPU%";' to see if the October 2007 Critical Patch Update was applied
    Affected if No CPU patch from October 2007 (or later) appears in the registry history, leaving the EM01 vulnerability unpatched

You are affected if you are running Oracle Database 10.1.0.5 or 10.2.0.3 with Enterprise Manager/Database Control web interface enabled and accessible, and the October 2007 CPU has not been applied.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) from October 2007 that addresses EM01, or upgrade to a supported Oracle Database version since these affected releases are long-end-of-life. Restrict network access to Enterprise Manager ports as an interim compensating control.

Recommended fix Moderate confidence

Oracle Database 19c or 21c (supported long-term release)

  1. Verify the current Oracle Database version using SELECT VERSION FROM V$INSTANCE;
  2. Check Oracle's official certification matrix for your operating system to identify supported Oracle Database versions.
  3. Plan an upgrade path: Oracle Database 10g (10.1/10.2) -> 11g -> 12c -> 19c/21c (recommended target).
  4. Review Oracle's upgrade documentation for the chosen target version, paying attention to compatibility settings and required pre-upgrade checks.
  5. Perform a full backup of the current database before initiating any upgrade process.
  6. Use the Database Upgrade Assistant (DBUA) for the upgrade process, or manually upgrade using export/import methods.
  7. After upgrade, verify that Database Control/Enterprise Manager is functioning correctly and reconfigure if necessary.
  8. Apply the latest Oracle Critical Patch Update (CPU) for the new database version to address other known vulnerabilities.
Caveat Upgrading from Oracle 10g to 19c/21c will require changes to applications, SQL queries, and potentially the compatibility parameter; extensive testing in a non-production environment is required before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Database Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5530 — 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-2007-5530 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