Database ServerDatabase / datastore · Oracle

CVE-2010-0903

HIGH · 7.8 CVSS v2.0 Published 2010-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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 Net Foundation Layer component in Oracle Database Server 9.2.0.8, 10.1.0.5, 10.2.0.4, 11.1.0.7, and 11.2.0.1, when running on Windows, allows remote attackers to affect 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 Database Server's Net Foundation Layer component on Windows platforms allows remote attackers to impact availability. The Net Foundation Layer handles Oracle network communications, and this flaw can be exploited remotely to cause denial of service. Affected versions span Oracle 9i through 11gR2 on Windows.

MitigationApply Oracle Critical Patch Updates (CPU) for the applicable version. Since this affects availability, schedule maintenance windows and ensure backups are in place before applying patches to production Oracle database instances on Windows.

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= 10.1.0.5= 10.2.0.4= 11.1.0.7= 11.2.0.1

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

AV:N/AC:L/Au:N/C:N/I:N/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 Windows platform
    Confirm the operating system hosting the Oracle Database Server is Windows. This vulnerability only applies to Windows platforms.
    Affected if The Oracle Database Server is running on a non-Windows platform, then this CVE does not apply.
  2. Identify installed Oracle Database version
    Run the query 'SELECT VERSION FROM V$INSTANCE;' or check the Oracle inventory to determine the exact Oracle Database version installed.
    Affected if The installed version is exactly 9.2.0.8, 10.1.0.5, 10.2.0.4, 11.1.0.7, or 11.2.0.1 on Windows.
  3. Confirm Oracle Net Listener is configured
    Check if the Oracle Net Listener (lsnrctl) is running and configured. Use 'lsnrctl status' command or check for listener.ora configuration file.
    Affected if The Net Foundation Layer handles Oracle network communications; if the listener is active and exposed to network, the vulnerability is reachable.
  4. Verify network exposure
    Review Oracle Net configuration (listener.ora, sqlnet.ora) and firewall rules to determine if the Oracle listener is accessible from remote hosts.
    Affected if The Oracle listener is reachable from remote network segments, making the denial of service exploit viable.

A Windows-based Oracle Database Server running any of the affected versions (9.2.0.8, 10.1.0.5, 10.2.0.4, 11.1.0.7, or 11.2.0.1) with an exposed Oracle Net Listener is vulnerable to this denial of service flaw.

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 applicable version. Since this affects availability, schedule maintenance windows and ensure backups are in place before applying patches to production Oracle database instances on Windows.

Fix this in Database Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-0903 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