# CVE-2006-5725: Information disclosure in n/a

> Remote attackers can determine the existence of directories on the AEP Smartgate SSL server by analyzing HTTP status codes returned for directory requests.

- **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:** No
- **Published:** 4 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-crw8-5r9p-8x8x

## What is CVE-2006-5725?

CVE-2006-5725 is a medium-severity vulnerability in n/a, published on 4 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SSL server in AEP Smartgate 4.3b allows remote attackers to determine existence of directories via a direct request for a directory URI, which returns different HTTP status codes for existing and non-existing directories.

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

## Which versions are affected by CVE-2006-5725?

It affects 1 product.


Products: Aep Networks Smartgate Ssl Server.

## How do I fix CVE-2006-5725?

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

## Is CVE-2006-5725 being exploited?

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

Public exploit code:

- AEP SmartGate 4.3b - 'GET' Arbitrary File Download (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5596](https://insights.sbomify.com/CVE-2006-5596/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-5725 and fix it if it is affected.

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

## Sources

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

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