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

> Remote attackers can list and read contents of arbitrary drives in Hosting Controller, exposing sensitive file system information.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3rgh-h4g7-m8pg

## What is CVE-2005-3038?

CVE-2005-3038 is a medium-severity vulnerability in n/a, published on 22 Sep 2005. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Hosting Controller 6.1 before Hotfix 2.4 allows remote attackers to list and read contents of arbitrary drives, related to "the PHP vulnerability."

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

It affects 1 product.


Products: Hosting Controller Hosting Controller.

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

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

## Is CVE-2005-3038 being exploited?

There is no known exploitation of CVE-2005-3038 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-6494](https://insights.sbomify.com/CVE-2007-6494/): Auth bypass in n/a (critical 10.0)
- [CVE-2002-0773](https://insights.sbomify.com/CVE-2002-0773/): Path traversal in n/a (critical 10.0)
- [CVE-2002-0774](https://insights.sbomify.com/CVE-2002-0774/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2002-0465](https://insights.sbomify.com/CVE-2002-0465/): Path traversal in n/a (critical 10.0)
- [CVE-2006-1764](https://insights.sbomify.com/CVE-2006-1764/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3038 is a medium-severity vulnerability in n/a, published on 22 Sep 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3038 in the wild and no public exploit code.

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-3038/ (Markdown: https://insights.sbomify.com/CVE-2005-3038/index.md)
```

## Sources

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

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