dbcve.org
Database 9iDatabase / datastore · Oracle

CVE-2008-1813

MEDIUM · 6.5 CVSS v2.0 Published 2008-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Multiple unspecified vulnerabilities in Oracle Database 9.0.1.5 FIPS+, 9.2.0.8, 9.2.0.8DV, 10.1.0.5, and 10.2.0.3 have unknown impact and remote unauthenticated or authenticated attack vectors related to (1) SYS.DBMS_AQ in the Advanced Queuing component, aka DB01; (2) Core RDBMS, aka DB03; (3) SDO_GEOM in Oracle Spatial, aka DB06; (4) Export, aka DB12; and (5) DBMS_STATS in Query Optimizer, aka DB13. NOTE: the previous information was obtained from the Oracle CPU. Oracle has not commented on reliable researcher claims that DB06 is SQL injection, and DB13 occurs when the OUTLN account is reset to use a hard-coded password.

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

Multiple remote vulnerabilities in Oracle Database 9.x and 10.x affect five components: Advanced Queuing (DBMS_AQ), Core RDBMS, Oracle Spatial (SDO_GEOM - claimed SQL injection), Export, and Query Optimizer (DBMS_STATS). Some vectors allow unauthenticated exploitation while DB13 requires the OUTLN account to be reset to a hard-coded password. The exact impact is unspecified by Oracle.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2008 or later to address these vulnerabilities; for DB13 specifically, ensure the OUTLN account password is properly managed and not reset to default credentials.

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 9iDatabase / datastore
Affected:= 9.0.1.5= 9.2.0.8= 9.2.0.8dv
Database ServerDatabase / datastore
Affected:= 9.0.1.5= 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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 installed Oracle Database version
    Connect to the database as a privileged user (e.g., SYS) and execute: SELECT VERSION FROM V$INSTANCE; or check the oratab / etc/oratab file for the installed Oracle home version.
    Affected if The version matches 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
  2. Check if Advanced Queuing (DBMS_AQ) is accessible
    Query SELECT owner, object_name FROM dba_objects WHERE object_name = 'DBMS_AQ' AND object_type = 'PACKAGE'; to verify the package exists and is accessible to potentially exploitable users.
    Affected if DBMS_AQ package exists and is granted to public or non-privileged users in a vulnerable version environment
  3. Check if Oracle Spatial (SDO_GEOM) is installed and exposed
    Query SELECT owner, object_name FROM dba_objects WHERE object_name = 'SDO_GEOM' AND object_type = 'PACKAGE'; Also verify which users have execute privileges on this package.
    Affected if SDO_GEOM package exists and is accessible to public or application users in a vulnerable version environment
  4. Check if DBMS_STATS is accessible to potentially exploitable users
    Query SELECT grantee, privilege FROM dba_tab_privs WHERE table_name = 'DBMS_STATS'; to identify who can execute this package.
    Affected if DBMS_STATS is granted to public or low-privileged users in a vulnerable version environment
  5. Verify OUTLN account status
    Query SELECT username, account_status, password_versions FROM dba_users WHERE username = 'OUTLN'; The DB13 flaw requires the OUTLN account with hard-coded password.
    Affected if OUTLN account exists and is unlocked/accessible in a vulnerable version environment

If the installed Oracle version matches 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3 AND any of the affected components (DBMS_AQ, SDO_GEOM, DBMS_STATS, or OUTLN account) are accessible to potentially unauthorized users, the environment is likely affected by CVE-2008-1813.

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 the relevant Oracle Critical Patch Update (CPU) for April 2008 or later to address these vulnerabilities; for DB13 specifically, ensure the OUTLN account password is properly managed and not reset to default credentials.

Fix this in Database 9i Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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