dbcve.org
Identity Driven ManagerApplication · Hp

CVE-2013-4811

HIGH · 10.0 CVSS v2.0 Published 2013-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

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 · unedited
UpdateDomainControllerServlet 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 adCert 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 confidence

HP ProCurve Manager's UpdateDomainControllerServlet fails to validate the adCert parameter, allowing unauthenticated remote attackers to upload arbitrary JSP files to the server's webroot. Since JSP files are executable, attackers can achieve remote code execution by requesting the uploaded files.

MitigationApply HP patches when available. Until then, restrict network access to the SNAC registration server port (default 5435) or disable the servlet via web.xml. Implement WAF rules to block .jsp upload attempts.

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
Identity Driven ManagerApplication
Affected:= 4.0
Procurve ManagerApplication
Affected:= 3.20= 4.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HP ProCurve Manager or HP Identity Driven Manager version
    Check the application's version through its About/Help dialog, installation directory readme files, or registry keys under HKLM\Software\HP\ProCurve Manager or similar HP product registry paths. Compare against affected versions: HP ProCurve Manager 3.20 or 4.0, HP Identity Driven Manager 4.0.
    Affected if The installed version matches exactly 3.20 or 4.0 for ProCurve Manager, or 4.0 for Identity Driven Manager.
  2. Verify the UpdateDomainControllerServlet is exposed
    Check the application's web.xml deployment descriptor (typically in conf or WEB-INF directory) for the servlet mapping for UpdateDomainControllerServlet. The servlet is typically accessible at /servlet/UpdateDomainControllerServlet or similar path under the application context.
    Affected if The UpdateDomainControllerServlet is mapped and the application web interface is reachable without authentication.
  3. Check network accessibility of SNAC registration port 5435
    Use netstat or ss to check if port 5435 (default SNAC registration server port) is listening on external interfaces, or scan the server from an external host using nmap -p 5435 <target>.
    Affected if Port 5435 is bound to 0.0.0.0 or accessible from untrusted networks without firewall filtering.
  4. Inspect webroot for unauthorized JSP files
    Search the application's web document root (typically the 'webapps' or 'deploy' directory) for any .jsp files that were not deployed as part of the legitimate application, especially in root or subdirectories accessible via HTTP.
    Affected if Unexpected .jsp files exist in web-accessible directories, particularly with suspicious names like shell, cmd, or random alphanumeric strings.
  5. Review access logs for exploitation attempts
    Examine HTTP access logs for POST requests to the UpdateDomainControllerServlet containing the adCert parameter, especially those submitting .jsp content or path traversal sequences. Look for unusual request patterns around the upload servlet.
    Affected if Logs show POST requests to UpdateDomainControllerServlet with unexpected parameter values or .jsp file extensions in the request body.

A system is affected if it runs HP ProCurve Manager 3.20/4.0 or HP Identity Driven Manager 4.0 with the UpdateDomainControllerServlet accessible over the network and either the vulnerable port 5435 is exposed or unexpected JSP files appear in the webroot.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply HP patches when available. Until then, restrict network access to the SNAC registration server port (default 5435) or disable the servlet via web.xml. Implement WAF rules to block .jsp upload attempts.

Fix this in Identity Driven Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4811 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4811 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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