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

> Remote attackers can obtain the web server path via a single quote in the PIProfile function, leaking sensitive path information in error messages.

- **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:** 22 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cv97-3hvj-jx45

## What is CVE-2006-4899?

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

### Official description

The ePPIServlet script in Computer Associates (CA) eTrust Security Command Center 1.0 and r8 up to SP1 CR2, when running on Windows, allows remote attackers to obtain the web server path via a "'" (single quote) in the PIProfile function, which leaks the path in an error message.

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

It affects 1 product.


Products: Broadcom Etrust Security Command Center.

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

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

## Is CVE-2006-4899 being exploited?

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

Public exploit code:

- CA eSCC r8/1.0 / eTrust Audit r8/1.5 - Web Server Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-4900](https://insights.sbomify.com/CVE-2006-4900/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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