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

> Remote attackers can obtain sensitive path information via invalid parameters when specific server options are enabled.

- **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:** 1 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p79v-mj8v-c6p4

## What is CVE-2005-4700?

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

### Official description

TellMe 1.2 and earlier, when the Server (o_Server) and HEAD (o_Head) options are enabled, allows remote attackers to obtain sensitive information via an invalid q_Host parameter, which reveals the full pathname of the application in an fsockopen error message.

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

It affects 1 product.


Products: Tellme Tellme.

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

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

## Is CVE-2005-4700 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4698](https://insights.sbomify.com/CVE-2005-4698/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4700 is a medium-severity vulnerability in n/a, published on 1 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4700 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-4700/ (Markdown: https://insights.sbomify.com/CVE-2005-4700/index.md)
```

## Sources

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

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