CVE-2002-1089
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 · uneditedrwcgi60 CGI program in Oracle Reports Server, by design, provides sensitive information such as the full pathname, which could enable remote attackers to use the information in additional attacks.
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 confidenceThe rwcgi60 CGI program in Oracle Reports Server discloses full filesystem pathnames by design, which could aid attackers in conducting path traversal, file inclusion, or other targeted attacks against the system.
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= 9.0.2= 6.0.8= 6.0.8.19CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Server is installedCheck for the presence of Oracle Reports Server components, commonly installed under ORACLE_HOME/reports60/, or look for the 'rwrun' or 'rwrun60' executables in the Oracle installation directory.Affected if Oracle Reports Server 6.0.8, 6.0.8.19, or Oracle Application Server 9.0.2 is installed.
-
Locate the rwcgi60 CGI programSearch for the rwcgi60 executable in typical Oracle CGI directories such as $ORACLE_HOME/bin/, $ORACLE_HOME/reports60/cgi/, or the web server's cgi-bin directory.Affected if The rwcgi60 CGI program exists in the environment.
-
Determine the Oracle Reports versionRun 'rwrun60 -V' or check the version information file in the reports60 directory, or query the Oracle Reports Server components via Oracle Application Server control utilities.Affected if The version is 6.0.8, 6.0.8.19, or the Oracle Application Server version is 9.0.2.
-
Check if CGI is web-exposedReview the web server configuration (httpd.conf, oc4j.conf, or equivalent) to see if the directory containing rwcgi60 is mapped to a web-accessible URL path.Affected if The rwcgi60 CGI is accessible via HTTP/HTTPS requests from the web.
-
Test for path disclosure in CGI responsesSend a request to the rwcgi60 CGI endpoint (e.g., via curl or browser) and examine any error messages or output for full filesystem paths.Affected if The CGI responses contain full absolute filesystem paths (such as /u01/app/oracle/...) rather than relative paths or generic messages.
A defender is affected if Oracle Reports Server 6.0.8/6.0.8.19 or Oracle Application Server 9.0.2 is installed with the rwcgi60 CGI program exposed via web and returning full filesystem paths in its output.
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 Oracle security patches if available, or configure the web server to filter sensitive path information from CGI responses, or disable the CGI if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1089 — 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-2002-1089 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