Application ServerApplication · Oracle

CVE-2006-0289

HIGH · 10.0 CVSS v2.0 Published 2006-01-18

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

NVD · unedited

Multiple unspecified vulnerabilities in Oracle Application Server 6.0.8.26(PS17) and E-Business Suite and Applications 11.5.10 have unspecified impact and attack vectors, as identified by Oracle Vuln# (1) REP05 and (2) REP06 in the Oracle Reports Developer component. NOTE: Oracle has not disputed reliable researcher claims that REP05 is the same as CVE-2005-2378 and REP06 is the same as CVE-2005-2371, both of which involve directory traversal.

Technical summary

dbcve analysis · moderate confidence

This CVE covers two vulnerabilities (REP05 and REP06) in Oracle Reports Developer component of Oracle Application Server 6.0.8.26 and E-Business Suite 11.5.10. Based on the researcher's claims that Oracle has not disputed, these are the same vulnerabilities as CVE-2005-2378 and CVE-2005-2371, both of which are directory traversal vulnerabilities allowing attackers to access files outside the web root through manipulated path parameters.

MitigationApply Oracle Critical Patch Updates (CPUs) for January 2006 or later, as these address the directory traversal issues in Oracle Reports Developer. If unsupported versions are in use, consider upgrading to a supported Oracle release or implementing web application firewall rules to block path traversal patterns (.., /, \) in request parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Application ServerApplication

Affected:= 6.0.8.26_ps17

E Business SuiteApplication

Affected:= 11.5.10

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle Reports Developer installation

Check if Oracle Reports Developer component is installed by examining the Oracle Application Server or E-Business Suite installation directories for the 'reports' web application (typically under $ORACLE_HOME/Apache/Apache/bin or similar reports-related paths). On the system, run: 'ls -la' on common Oracle homes or check Oracle Inventory for installed components.

Affected if Oracle Reports Developer component is present in the Oracle installation
Determine Oracle Application Server version

Check the Oracle Application Server version by running 'opatch lsinventory' or examining the ORACLE_HOME/oraInst.loc file. Also check the patch level using 'opatch lsinventory -detail' to identify if patch set 6.0.8.26_ps17 or earlier is applied.

Affected if Version is 6.0.8.26 with patch set version ps17 or earlier
Determine Oracle E-Business Suite version

Check the E-Business Suite version by examining the $APPL_TOP/../OracleEBSApp.properties or running SQL query: 'SELECT release_name FROM apps.fnd_product_groups' connected as APPS.

Affected if Version is 11.5.10 or earlier
Verify Oracle Reports web interface is exposed

Check if the Oracle Reports web interface (rwrun.jar, rwrun, or /reports/ servlet) is accessible by examining the Oracle HTTP Server configuration files (httpd.conf or oracle_apache.conf) for mod_oc4j or mod_reports configuration entries. Test by attempting to access common Reports URLs: http://hostname:port/reports/rwrun

Affected if The Oracle Reports Developer web interface is accessible via HTTP/HTTPS without authentication
Check for vulnerable path parameter handling

Examine the Oracle Reports web configuration for the presence of the directory traversal vulnerability by reviewing the reports web.xml deployment descriptor and checking if parameter validation is implemented. Look for the 'server' and 'destype' parameters in the Reports servlet configuration.

Affected if Reports web interface accepts parameters without proper path validation (checking for '..' traversal patterns in requests)

The environment is affected if Oracle Reports Developer is installed and accessible, running Oracle Application Server 6.0.8.26_ps17 or earlier, or Oracle E-Business Suite 11.5.10 or earlier, with the Reports web interface exposed without path traversal protections.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Updates (CPUs) for January 2006 or later, as these address the directory traversal issues in Oracle Reports Developer. If unsupported versions are in use, consider upgrading to a supported Oracle release or implementing web application firewall rules to block path traversal patterns (.., /, \) in request parameters.

Fix this in Application Server Scoped from the published advisory

Consultation8.0 h
Implementation24.0 h
Testing12.0 h
Review / QA6.0 h

50.0 hours of engineering $8,800

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-0289 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-0289?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 13.0%

Affects: Application Server

Remediation

A high-priority fix

Fix this in Application Server 50 hrs · Severe

Typical engagement from $8,800

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2006-0289 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References