CVE-2016-1524 — Prosafe Network Management Software 300
CRITICALCVE-2016-1524 is a critical-severity (CVSS 9.6) vulnerability in netgear prosafe network management software 300. 2 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
Multiple unrestricted file upload vulnerabilities in NETGEAR Management System NMS300 1.5.0.11 and earlier allow remote attackers to execute arbitrary Java code by using (1) fileUpload.do…
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2016-1524 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 397,508 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Multiple unrestricted file upload vulnerabilities in NETGEAR Management System NMS300 1.5.0.11 and earlier allow remote attackers to execute arbitrary Java code by using (1) fileUpload.do or (2) lib-1.0/external/flash/fileUpload.do to upload a JSP file, and then accessing it via a direct request for a /null URI.
Affected Products
prosafe network management software 300netgearResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Netgear NMS300 ProSafe Network Management System - Multiple Vulnerabilities
by Pedro Ribeiro · Feb 4, 2016
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every netgear prosafe network management software 300 deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2016-1524 yet — track the netgear prosafe network management software 300 advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2016-1524 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.