dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2002-1156

MEDIUM · 5.0 CVSS v2.0 Published 2002-10-11
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 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 · unedited
Apache 2.0.42 allows remote attackers to view the source code of a CGI script via a POST request to a directory with both WebDAV and CGI enabled.

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 confidence

In Apache 2.0.42, when both WebDAV and CGI modules are enabled, a remote attacker can send a POST request to a directory containing CGI scripts and receive the script's source code instead of having it executed. This occurs due to improper interaction between the WebDAV and CGI handlers.

MitigationUpgrade to a patched Apache version or disable the WebDAV module if not required; alternatively, ensure CGI scripts are not located within WebDAV-accessible directories.

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
Affected:= 2.0.42

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.

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 checks

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

  1. Check Apache version
    Run 'httpd -v' or 'apache2 -v' to determine the installed Apache version
    Affected if Version is 2.0.42 exactly
  2. Verify WebDAV module is loaded
    Check for 'mod_dav' or 'mod_dav_fs' in the loaded modules list using 'httpd -M' or 'apache2ctl -M'
    Affected if WebDAV module (mod_dav) appears in the loaded modules list
  3. Verify CGI module is enabled
    Check for 'mod_cgi' in the loaded modules list using 'httpd -M' or 'apache2ctl -M'; also verify CGI is allowed in configuration with 'Options +ExecCGI' or 'ScriptAlias' directives
    Affected if CGI module (mod_cgi) is loaded and CGI execution is permitted in any directory configuration
  4. Identify CGI script locations
    Search for CGI script directories - look for 'ScriptAlias' directives or 'Options +ExecCGI' in Apache configuration files, and list CGI scripts in those directories
    Affected if CGI scripts exist in directories configured within or under the DocumentRoot (or any WebDAV-accessible location)
  5. Confirm WebDAV access to CGI directories
    Verify that the directories containing CGI scripts are accessible via WebDAV - check that they are not excluded by DAV disable directives and are within the DocumentRoot scope
    Affected if The CGI script directories are served by Apache and accessible via WebDAV (not explicitly excluded from DAV operations)

You are affected if running Apache 2.0.42 with both WebDAV and CGI modules enabled, and CGI scripts exist within WebDAV-accessible directories.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched Apache version or disable the WebDAV module if not required; alternatively, ensure CGI scripts are not located within WebDAV-accessible directories.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1156 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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