dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2010-0071

HIGH · 10.0 CVSS v2.0 Published 2010-01-13
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 Listener component in Oracle Database 9.2.0.8, 9.2.0.8DV, 10.1.0.5, 10.2.0.4, and 11.1.0.7 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 the Oracle Database Listener component affecting versions 9.2.0.8 through 11.1.0.7 allows remote attackers to impact confidentiality, integrity, and availability via unknown vectors.

MitigationApply Oracle Critical Patch Update (CPU) released January 2010 or later that addresses this vulnerability, or upgrade to a supported Oracle Database version beyond 11.1.0.7.

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:= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.4= 11.1.0.7

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. Verify Oracle Listener is running
    On the database server, check for the Oracle Listener process (tnslsnr) using OS commands like 'ps -ef | grep tnslsnr' on Unix/Linux or check Services on Windows
    Affected if The Listener process is not found, meaning the component is not in use
  2. Obtain Oracle Listener version
    Run 'lsnrctl version' from the Oracle home directory or use 'lsnrctl STATUS' to see version details
    Affected if The reported version matches 9.2.0.8, 9.2.0.8dv, 10.1.0.5, 10.2.0.4, or 11.1.0.7 exactly
  3. Confirm Oracle Database Server version
    Connect to the database as SYSDBA and run 'SELECT VERSION FROM V$INSTANCE;' or check the Oracle inventory for installed versions
    Affected if The database version corresponds to one of the affected Listener versions listed in the CVE
  4. Check Listener configuration
    Run 'lsnrctl STATUS' and review the output for any non-default or suspicious configurations in listener.ora
    Affected if The Listener is exposed to network (TCP) and the version matches affected ranges - the vulnerability allows remote impact

You are affected if the Oracle Database Listener is running and its version is exactly 9.2.0.8, 9.2.0.8dv, 10.1.0.5, 10.2.0.4, or 11.1.0.7.

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) released January 2010 or later that addresses this vulnerability, or upgrade to a supported Oracle Database version beyond 11.1.0.7.

Recommended fix Moderate confidence

Oracle Database 11.2.0.x or higher (11.2.0.7+ recommended)

  1. 1. Identify the current Oracle Database version using: SELECT VERSION FROM V$INSTANCE;
  2. 2. For Oracle Database 9.2.x, 10.1.x, and 10.2.x, upgrade to a supported, patched version (11.2.0.x or higher) as these older versions are no longer supported by Oracle.
  3. 3. If upgrading is not immediately feasible, apply the January 2010 Critical Patch Update (CPU) which addresses CVE-2010-0071.
  4. 4. Download the appropriate patch from My Oracle Support (support.oracle.com) using your Oracle SSO credentials.
  5. 5. Review Oracle Support Note 1089033.1 for CPU patching procedures and prerequisites.
  6. 6. Test the patch in a non-production environment before applying to production.
  7. 7. After patching/upgrading, validate the Listener component is operational: lsnrctl status
Caveat Major version upgrades from 9i/10g to 11g may require application compatibility testing and SQL rewrites; deprecated features in 11g may need remediation.

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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