CVE-2013-4811 in the critical feed json
UpdateDomainControllerServlet in the SNAC registration server in HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, and Identity Dr…
published 13y ago modified 4mo ago also EUVD-2013-4656
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 71.3%
- EPSS 71.3% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
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.
Is CVE-2013-4811 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/http/hp_pcm_snac_update_domain)
- Published
Exploit prediction
71.29% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/http/hp_pcm_snac_update_domain HP ProCurve Manager SNAC UpdateDomainControllerServlet File Upload metasploit exploit, excellent rank, 2013-09-09
- EDB-28336 HP ProCurve Manager - SNAC UpdateDomainControllerServlet Arbitrary File Upload (Metasploit) remote, 2013-09-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
h20565.www2.hp.com
/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?docId=emr_na-c03897409
vendor-advisory
-
securitytracker.com
/id/1029010
vdb-entry
- zerodayinitiative.com /advisories/ZDI-13-226/
-
secunia.com
/advisories/54788
third-party-advisory
Sources
- CVE List CVE-2013-4811
- NVD CVE-2013-4811
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.