CVE-2005-2371
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 · uneditedDirectory traversal vulnerability in Oracle Reports 6.0, 6i, 9i, and 10g allows remote attackers to overwrite arbitrary files via (1) "..", (2) Windows drive letter (C:), and (3) absolute path sequences in the desname parameter. NOTE: this issue was probably fixed by REP06 in CPU Jan 2006, in which case it overlaps CVE-2006-0289.
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 · high confidenceDirectory traversal vulnerability in Oracle Reports (versions 6.0, 6i, 9i, and 10g) allows remote attackers to overwrite arbitrary files by using path traversal sequences (..), Windows drive letters (C:), or absolute paths in the desname parameter.
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= 6.0= 6i= 9i= 10gCVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle Reports is installedCheck for Oracle Reports installation directories (e.g., $ORACLE_HOME/reports, ORACLE_HOME/bin/rwrun, ORACLE_HOME/reports/server), or query the Oracle inventory using opatch lsinventory or Oracle Universal InstallerAffected if Oracle Reports component is found on the system
-
Determine the installed Oracle Reports versionRun 'rwrun -v' or 'rwrun help=y' from the Reports bin directory, or check the version in the Oracle inventory. For 9i/10g, also check the rwservlet configuration file (rwservlet.properties) or the Oracle Enterprise Manager consoleAffected if The version matches 6.0, 6i, 9i, or 10g exactly (note: this vulnerability affects specific point releases within these version families)
-
Verify the Oracle Reports web interface is accessibleTest access to the Reports web servlet endpoint (typically at /reports/rwservlet or /reports/rwrun) on the Oracle Application Server or Oracle Forms/Reports serverAffected if The web interface is exposed and reachable over the network
-
Confirm the desname parameter accepts path traversal inputSend a test HTTP request to the Reports servlet with a modified desname parameter containing traversal sequences (e.g., desname=../filename) and observe whether the server processes or returns information about the requested pathAffected if The desname parameter allows path traversal sequences (..), absolute paths, or drive letters without rejection
The environment is affected if Oracle Reports versions 6.0, 6i, 9i, or 10g is installed, the web interface is accessible, and the desname parameter accepts path traversal sequences without input validation.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the REP06 patch from CPU Jan 2006 (or subsequent security patches), or upgrade to a supported Oracle Reports version; implement input validation on the desname parameter to reject path traversal sequences.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2371 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-2371 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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