CVE-2013-4812
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 · uneditedUpdateCertificatesServlet in the SNAC registration server in HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, and Identity Driven Manager (IDM) 4.0 does not properly validate the fileName argument, which allows remote attackers to upload .jsp files and consequently execute arbitrary code via unspecified vectors, aka ZDI-CAN-1743.
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 UpdateCertificatesServlet in HP ProCurve Manager's SNAC registration server fails to validate the fileName parameter, allowing unauthenticated remote attackers to upload arbitrary JSP files to the web server's document root and achieve remote code execution.
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 installed HP management productCheck system for HP ProCurve Manager or HP Identity Driven Manager installations. Look for installation directories or check installed programs. Common paths may include C:\Program Files\HP or similar.Affected if The product installed is HP ProCurve Manager version 3.20 or 4.0, or HP Identity Driven Manager version 4.0
-
Confirm SNAC registration server is runningCheck for processes related to SNAC (Secure Network Access Control) or the ProCurve Manager service. Look for Java processes running the management application or check Windows services for HP management services.Affected if SNAC registration server component is actively running
-
Verify UpdateCertificatesServlet is accessibleCheck if the web application exposes the UpdateCertificatesServlet endpoint. This is typically accessed via URL path containing 'UpdateCertificatesServlet' or 'SNAC' in the registration server context. Attempt to access the servlet URL if known or check web.xml deployment descriptors.Affected if The UpdateCertificatesServlet is exposed and accessible via the web interface
-
Check for unexpected JSP files in web rootInspect the web server's document root directory for unfamiliar JSP files that were not intentionally deployed. Look for files with unusual names or recent creation dates in the web root.Affected if Arbitrary JSP files exist in the web document root that were not intentionally placed there by administrators
If HP ProCurve Manager 3.20/4.0 or HP Identity Driven Manager 4.0 is installed with the SNAC registration server running and the UpdateCertificatesServlet is accessible, the system is vulnerable to unauthenticated JSP file upload and remote code execution.
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 if available; if no patch exists, restrict network access to the SNAC registration server and implement strict fileName validation to prevent .jsp file uploads.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4812 — 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-4812 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