dbcve.org
Application ServerApplication · Oracle

CVE-2004-1371

HIGH · 9.0 CVSS v2.0 Published 2004-08-04
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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
Stack-based buffer overflow in Oracle 9i and 10g allows remote attackers to execute arbitrary code via a long token in the text of a wrapped procedure.

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
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Application ServerApplication
Affected:all versions= 9.0.2= 9.0.2.0.0= 9.0.2.0.1= 9.0.2.1= 9.0.2.2= 9.0.2.3= 9.0.3= 9.0.3.1= 9.0.4= 9.0.4.0= 9.0.4.1
Collaboration SuiteApplication
Affected:= release_1
Database ServerDatabase / datastore
Affected:= 9i_application_server
E Business SuiteApplication
Affected:= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.5.5= 11.5.6= 11.5.7= 11.5.8= 11.5.9
Enterprise ManagerApplication
Affected:= 9= 9.0.1
Enterprise Manager Database ControlDatabase / datastore
Affected:= 10.1.2
Enterprise Manager Grid ControlApplication
Affected:= 10.1.0.2
Oracle10gDatabase / datastore
Affected:= enterprise_9.0.4_.0= enterprise_10.1.0.2= personal_9.0.4_.0= personal_10.1_.0.2= standard_9.0.4_.0= standard_10.1_.0.2

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

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

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
Patch available Apply the vendor patch
Vendor patch www.ngssoftware.com →
Recommended fix High confidence

Upgrade to a supported Oracle version (Oracle 11gR2 or higher, preferably Oracle 19c or 21c for long-term support)

  1. Identify the exact Oracle component affected (Database Server, Application Server, or Enterprise Manager) by reviewing system documentation
  2. Backup all Oracle databases and configuration files before making any changes
  3. Contact Oracle Support to obtain the appropriate patch for this vulnerability (Oracle Critical Patch Update from January 2005 or later)
  4. If Oracle Support cannot provide a patch for your specific version, plan an upgrade to a supported Oracle version
  5. For Database Server: Upgrade to a supported Oracle version (11gR2, 12c, 18c, 19c, or 21c as appropriate for your environment)
  6. For Application Server: Upgrade to Oracle WebLogic Server or a supported Oracle Fusion Middleware version
  7. After upgrade, verify the wrapped procedure functionality works correctly with the new Oracle version
  8. Apply latest Oracle Critical Patch Updates (CPUs) after upgrade to ensure all security patches are applied
Caveat Upgrading from Oracle 9i/10g to modern Oracle versions may require significant compatibility testing; wrapped procedures may need rewrites; legacy application code may need modifications for compatibility with newer Oracle database features and deprecated/removed functionality

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

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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