Procurve Manager vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited7 versions
The short answer

Procurve Manager is made by HP. We track 6 published vulnerabilities in it, across 7 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Procurve Manager, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Procurve Manager flaw added to the known-exploited list is CVE-2013-4810, on 25 March 2022. We keep watching the known-exploited list.

Versions

Which versions of Procurve Manager do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2013-4810Exploited list, 25 Mar 2022

    HP Multiple Products Remote Code Execution Vulnerability

    3.204.0
Known exploited

Which Procurve Manager vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2013-4810CriticalKnown exploited
    HP Multiple Products Remote Code Execution Vulnerability

    HP ProCurve Manager (PCM), PCM+, Identity Driven Manager (IDM), and Application Lifecycle Management allow remote attackers to execute arbitrary code via a marshalled object to (1) EJBInvokerServlet or (2)...

    Chance of use79%Known exploited since25 Mar 2022
Exploit likelihood

Which Procurve Manager flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 79%
    CVE-2013-4810CriticalKnown exploited

    HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, Identity Driven Manager (IDM) 4.0, and Application Lifecycle Management allow remote attackers to execute arbitrary code via a marshalled object to (1)...

    CVSS9.8Published16 Sep 2013
  2. 8.5%

    The 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,...

    CVSS10.0Published16 Sep 2013
  3. 2.4%

    Unspecified vulnerability in HP ProCurve Manager and HP ProCurve Manager Plus 2.3 and earlier allows remote attackers to obtain sensitive information from the ProCurve Manager server via unknown attack vectors.

    CVSS5.0Published15 Apr 2009
Precursor Intelligence

Running Procurve Manager? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 6 published vulnerabilities listed under the name Procurve Manager, across 7 versions. The most recent Procurve Manager flaw added to the known-exploited list is CVE-2013-4810, on 25 March 2022.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2013-4810.

Each flaw names its own versions, usually as ranges. The newest, CVE-2013-4810, affects 3.20, 4.0. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Procurve Manager. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.