Application ServerApplication · Oracle

CVE-2002-1635

MEDIUM · 5.0 CVSS v2.0 Published 2002-12-31

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

59/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Apache configuration file (httpd.conf) in Oracle 9i Application Server (9iAS) uses a Location alias for /perl directory instead of a ScriptAlias, which allows remote attackers to read the source code of arbitrary CGI files via a URL containing the /perl directory instead of /cgi-bin.

Technical summary

dbcve analysis · high confidence

The Apache httpd.conf in Oracle 9iAS uses a Location alias directive for the /perl directory instead of ScriptAlias, causing the web server to return the plaintext source code of CGI scripts rather than executing them when accessed via /perl URLs.

MitigationReplace the Location alias with ScriptAlias for the /perl directory in httpd.conf and verify that CGI scripts execute properly instead of revealing source code.

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:all versions

CVSS breakdown

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?

dbcve checks

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

Confirm Oracle Application Server installation

Look for Oracle Application Server installation directories (ORACLE_HOME) or check for Apache processes with Oracle branding. Common locations include $ORACLE_HOME/Apache/Apache/ or /opt/oracle/

Affected if Oracle Application Server is installed and running
Locate the httpd.conf configuration file

Find the Apache httpd.conf in Oracle 9iAS, typically under ORACLE_HOME/Apache/Apache/conf/httpd.conf or similar Oracle-specific Apache directory

Affected if httpd.conf exists and is used by the Oracle Apache instance
Search for /perl directory configuration

Search httpd.conf for any directive referencing '/perl' using grep or manual inspection. Look for lines containing 'perl' and check what directive type precedes the path

Affected if A configuration directive for /perl directory is found in httpd.conf
Identify directive type for /perl

Examine whether the /perl directory uses 'Location' with 'Alias', 'ScriptAlias', or 'ScriptAliasMatch' directive. Check the exact configuration syntax used

Affected if The configuration uses 'Location' with 'Alias' directive for /perl instead of 'ScriptAlias' or 'ScriptAliasMatch'
Test CGI script execution via /perl URL

Place a test CGI script in the /perl directory (or use an existing one) and access it via a browser using the /perl URL path. Verify if source code is returned in plaintext or if the script executes normally

Affected if Accessing CGI scripts via /perl URL returns plaintext source code instead of executed output

A system is affected if Oracle Application Server is running with an httpd.conf that contains a Location alias directive (instead of ScriptAlias) for the /perl directory, causing CGI source code to be disclosed when accessed via web.

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

Replace the Location alias with ScriptAlias for the /perl directory in httpd.conf and verify that CGI scripts execute properly instead of revealing source code.

Fix this in Application Server Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2002-1635 — 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-2002-1635 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2002-1635?

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 5.0 Medium

Exploit likelihood EPSS, next 30 days 4.4%

Affects: Application Server

Remediation

Need this fixed?

Fix this in Application Server 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2002-1635 and return a fixed quote.

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