CVE-2013-4813
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 · uneditedThe Agent (aka AgentController) servlet in HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, and Identity Driven Manager (IDM) 4.0 allows remote attackers to execute arbitrary commands via a HEAD request, aka ZDI-CAN-1745.
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 confidenceThe AgentController servlet in HP ProCurve Manager (PCM), PCM+, and Identity Driven Manager contains a command injection vulnerability allowing remote attackers to execute arbitrary OS commands via specially crafted HEAD HTTP requests.
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= 4.0= 3.20= 4.0CVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Identify if HP ProCurve Manager or Identity Driven Manager is installedCheck for installation directories such as C:\Program Files\HP\ProCurve Manager or /opt/hp/pcm, or look for service entries named 'HP ProCurve Manager' or 'HP Identity Driven Manager' in Windows services or Unix init scriptsAffected if The product is installed on the system
-
Determine the installed versionCheck version files in the installation directory, or look at the application GUI login page banner, or query the Windows service version propertyAffected if Version equals 3.20 or 4.0 for HP ProCurve Manager, or version equals 4.0 for HP Identity Driven Manager
-
Verify the AgentController servlet is accessibleAttempt to access the URL path /agent/AgentController or /AgentController via HTTP HEAD request to the management interface (port 8080 or 443 typically)Affected if The servlet responds to requests, indicating the vulnerable component is exposed
-
Check network exposure of management interfaceReview firewall rules and network configuration to determine if ports 8080, 8443, or other management ports used by PCM/IDM are accessible from untrusted networksAffected if The management interface is reachable from networks outside the trusted administrative zone
A system is affected if HP ProCurve Manager version 3.20 or 4.0, or HP Identity Driven Manager version 4.0 is installed and the AgentController servlet is network-accessible
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 dataApply HP vendor patches for this vulnerability; if patches are unavailable, implement strict network segmentation to limit access to management interfaces and consider upgrading to supported product versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4813 — 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-2013-4813 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