HTTP ServerWeb server / proxy · Apache
CVE-2002-1592
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 · uneditedThe ap_log_rerror function in Apache 2.0 through 2.035, when a CGI application encounters an error, sends error messages to the client that include the full path for the server, which allows remote attackers to obtain sensitive information.
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 confidenceThe ap_log_rerror function in Apache HTTP Server versions 2.0 through 2.035 leaks the full server filesystem path in error messages returned to clients when CGI applications encounter errors, allowing remote attackers to enumerate server directory structures.
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
HTTP ServerWeb server / proxy
= 2.0= 2.0.28= 2.0.32= 2.0.35CVSS 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 installed Apache versionRun 'httpd -v' or 'apache2 -v' to retrieve the server version numberAffected if The version matches 2.0, 2.0.28, 2.0.32, or 2.0.35, or falls between 2.0 and 2.035 inclusive
-
Verify CGI module is enabledCheck for the presence of 'mod_cgi' in the loaded modules list using 'httpd -M' or 'apache2ctl -M', or look for 'LoadModule cgi_module' in the httpd.conf configuration fileAffected if CGI module is loaded and CGI scripts are executable on the server
-
Check if custom error document handling is configuredSearch the httpd.conf or included configuration files for 'ErrorDocument' directives that handle 500 or other CGI-related error codesAffected if No custom ErrorDocument directives are defined for CGI error responses, allowing default Apache error messages to leak paths
-
Inspect default error response behaviorTrigger a CGI error by requesting a CGI script that produces an error (such as a script with syntax errors or missing dependencies) and examine the returned error pageAffected if The error response contains the full server filesystem path (for example, paths like '/usr/local/apache/...')
You are affected if your Apache version is 2.0 through 2.035, CGI is enabled, and error responses expose the server's full filesystem path.
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 dataUpgrade Apache to version 2.036 or later, or configure custom error handlers to suppress detailed path information in CGI error responses.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1592 — 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-1592 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