dbcve.org
AwstatsApplication

CVE-2005-2732

MEDIUM · 5.0 CVSS v2.0 Published 2005-08-30
Fix available
A fix is available. Upgrade to after 6.4 or later.
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
AWStats 6.4, and possibly earlier versions, allows remote attackers to obtain sensitive information via a file that does not exist in the config parameter, which reveals the path in an error message.

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 confidence

AWStats 6.4 and earlier versions contains a path disclosure vulnerability where the application reveals the full server filesystem path in error messages when an invalid or non-existent file is specified in the config parameter. This information disclosure aids attackers in reconnaissance by exposing server directory structures.

MitigationImplement input validation on the config parameter to reject invalid values, and configure custom error handlers that return generic error messages without exposing filesystem paths.

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
AwstatsApplication
Affected:<= 6.4

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. Identify AWStats installation and version
    Locate the AWStats installation directory (commonly in /usr/local/awstats, /var/www/awstats, or similar). Check the awstats.pl script or VERSION file for the version number.
    Affected if Installed version is 6.4 or any version lower than 6.4
  2. Verify AWStats is web-accessible
    Confirm the AWStats CGI script (awstats.pl) is accessible via HTTP/HTTPS on your web server.
    Affected if AWStats is accessible over the web and responds to requests
  3. Test for path disclosure via config parameter
    Send an HTTP request to awstats.pl with an invalid or non-existent config parameter, such as ?config=invalidconfig123. Inspect the error response for any filesystem paths.
    Affected if The error message displays a full server filesystem path (e.g., /var/www/html/awstats/...)

Your environment is affected if AWStats version 6.4 or earlier is installed and web-accessible, and requesting an invalid config parameter exposes the full server path in the error response.

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
Upgrade available Upgrade to a release after 6.4
Interim mitigation

Implement input validation on the config parameter to reject invalid values, and configure custom error handlers that return generic error messages without exposing filesystem paths.

Fix this in Awstats Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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