# CVE-2007-5413: Path traversal in n/a

> Remote attackers can read arbitrary files on HP OpenView Configuration Management servers by exploiting path traversal via tilde references in URLs.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 29 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7v4w-hvhc-jxvp

## What is CVE-2007-5413?

CVE-2007-5413 is a high-severity path traversal vulnerability in n/a, published on 29 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

httpd.tkd in Radia Integration Server in Hewlett-Packard (HP) OpenView Configuration Management (CM) Infrastructure 4.0 through 4.2i and Client Configuration Manager (CCM) 2.0 allows remote attackers to read arbitrary files via URLs containing tilde (~) references to home directories, as demonstrated by ~root.

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

## Which versions are affected by CVE-2007-5413?

It affects 2 products.


Products: Hp Openview Client Configuraton Manager, Hp Openview Configuration Management.

## How do I fix CVE-2007-5413?

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

## Is CVE-2007-5413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5782](https://insights.sbomify.com/CVE-2006-5782/): Missing authorization in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5413 and fix it if it is affected.

What it is: CVE-2007-5413 is a high-severity path traversal vulnerability in n/a, published on 29 Oct 2007. 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-2007-5413 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-2007-5413/ (Markdown: https://insights.sbomify.com/CVE-2007-5413/index.md)
```

## Sources

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

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