CVE-2007-5413
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhttpd.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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in httpd.tkd in Radia Integration Server (part of HP OpenView CM Infrastructure 4.0-4.2i and CCM 2.0) allows remote attackers to read arbitrary files by using tilde (~) characters in URLs to reference home directories (e.g., ~root).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0= 4.0= 4.1= 4.2= 4.2iCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify HP OpenView product installation and versionCheck for installation of HP OpenView Configuration Management (versions 4.0, 4.1, 4.2, 4.2i) or HP OpenView Client Configuration Manager version 2.0. On Windows, inspect Add/Remove Programs or check the installation directory. On Unix/Linux, check the software inventory or installation logs.Affected if The product is installed and matches version 4.0, 4.1, 4.2, 4.2i, or 2.0.
-
Confirm Radia Integration Server component presenceLocate the httpd.tkd file within the installation directory. This file is part of the Radia Integration Server component. Search in typical installation paths such as /opt/HP/OpenView or C:\Program Files\HP\OpenView.Affected if The httpd.tkd file exists in the installation directory.
-
Check if HTTP service is accessibleAttempt to access the web service on the default HTTP port (typically port 8080 or 80) for the Radia Integration Server. Verify that the httpd.tkd endpoint responds to HTTP requests.Affected if The web interface is accessible and httpd.tkd responds to requests.
-
Test for tilde-based path traversal vulnerabilitySend an HTTP request to httpd.tkd with a tilde character and home directory reference, such as /~root/ or /~username/. For example: GET /httpd.tkd/~root/etc/passwd HTTP/1.1. Observe if the server returns file contents outside the web root.Affected if The server returns the contents of arbitrary files when using tilde characters in the URL.
A user is affected if HP OpenView Configuration Management versions 4.0-4.2i or CCM version 2.0 is installed, the Radia Integration Server httpd.tkd component is accessible, and the server responds to tilde-based path traversal requests by returning arbitrary file contents.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of HP OpenView Configuration Management or, if upgrades are not feasible, deploy a web application firewall or URL filtering to block requests containing tilde characters.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-5413 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data