# CVE-2005-0435: Information disclosure in n/a

> Remote attackers can read server web logs by manipulating parameters in AWStats, exposing sensitive traffic data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0435, GHSA-vrvm-7gw5-cw9h

## What is CVE-2005-0435?

CVE-2005-0435 is a medium-severity vulnerability in n/a, published on 15 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

awstats.pl in AWStats 6.3 and 6.4 allows remote attackers to read server web logs by setting the loadplugin and pluginmode parameters to rawlog.

## Which versions are affected by CVE-2005-0435?

It affects 1 product.


Products: Awstats Awstats.

## How do I fix CVE-2005-0435?

Upgrade to a fixed version.

## Is CVE-2005-0435 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0435 exists.

Public exploit code:

- AWStats 6.4 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-29600](https://insights.sbomify.com/CVE-2020-29600/): Path traversal in n/a (critical 9.8)
- [CVE-2017-1000501](https://insights.sbomify.com/CVE-2017-1000501/): Path traversal in n/a (critical 9.8)
- [CVE-2025-63261](https://insights.sbomify.com/CVE-2025-63261/): Command injection in n/a (high 7.8)
- [CVE-2010-4367](https://insights.sbomify.com/CVE-2010-4367/): Code injection in n/a (high 7.5)
- [CVE-2010-4368](https://insights.sbomify.com/CVE-2010-4368/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0435 and fix it if it is affected.

What it is: CVE-2005-0435 is a medium-severity vulnerability in n/a, published on 15 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0435 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-0435/ (Markdown: https://insights.sbomify.com/CVE-2005-0435/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-0435
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-0435
- OSV: https://osv.dev/vulnerability/CVE-2005-0435

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-0435/
Summaries are generated and may contain mistakes; the official description above is the record.