Unspecified vulnerability in HP MPIO Device Specific Module Manager before 4.02.00 allows local users to gain privileges via unknown vector…

published 2014-09-28 12y ago modified 2026-06-17 4mo ago also EUVD-2014-2671

cvss: 4.6; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits: 0; none known

Unspecified vulnerability in HP MPIO Device Specific Module Manager before 4.02.00 allows local users to gain privileges via unknown vectors.

Patch / fix

links 1

h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?docId… advisory

Is CVE-2014-2639 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 Fencer

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	4.6	AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

h20566.www2.hp.com /portal/site/hpsc/template.PAGE/public/kb/docDisplay/?docId=emr_na-c04048122
vendor-advisory, patch

Sources

CVE List CVE-2014-2639
NVD CVE-2014-2639

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.