# CVE-2018-10245: Information disclosure in n/a

> Remote attackers can obtain the full server path of the configuration file via specific parameters, exposing internal directory structures.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** No
- **Published:** 20 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-10245, GHSA-ccww-jx9f-9pm9, UBUNTU-CVE-2018-10245

## What is CVE-2018-10245?

CVE-2018-10245 is a medium-severity vulnerability in n/a, published on 20 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Full Path Disclosure vulnerability in AWStats through 7.6 allows remote attackers to know where the config file is allocated, obtaining the full path of the server, a similar issue to CVE-2006-3682. The attack can, for example, use the awstats.pl framename and update parameters.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-10245?

It affects 1 product.


Products: Awstats Awstats.

## How do I fix CVE-2018-10245?

No fix has been published for CVE-2018-10245 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-10245 being exploited?

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

Public exploit code:

- AWStats <= 7.5 - Full Path Disclosure (nuclei): http/cves/2018/CVE-2018-10245.yaml

## 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-2018-10245 and fix it if it is affected.

What it is: CVE-2018-10245 is a medium-severity vulnerability in n/a, published on 20 Apr 2018. 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-2018-10245 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-2018-10245/ (Markdown: https://insights.sbomify.com/CVE-2018-10245/index.md)
```

## Sources

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

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