CVE-2014-2630 json
Unspecified vulnerability in HP Operations Agent 11.00, when Glance is used, allows local users to gain privileges via unknown vectors.
published 12y ago modified 4mo ago also EUVD-2014-2662
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.1%
- EPSS 7.1% chance of exploitation in 30 days, percentile 94%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
Unspecified vulnerability in HP Operations Agent 11.00, when Glance is used, allows local users to gain privileges via unknown vectors.
Is CVE-2014-2630 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
- Published
- First public exploit (Metasploit exploit/linux/local/hp_xglance_priv_esc)
Exploit prediction
7.08% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/local/hp_xglance_priv_esc HP Performance Monitoring xglance Priv Esc metasploit exploit, great rank, 2014-11-19
- EDB-48000 xglance-bin 11.00 - Privilege Escalation local, 2020-02-05
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
References
-
h20564.www2.hp.com
/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04394554
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95181
vdb-entry
-
secunia.com
/advisories/60041
third-party-advisory
-
securitytracker.com
/id/1030702
vdb-entry
- packetstormsecurity.com /files/156206/xglance-bin-Local-Root-Privilege-Escalation.html
-
seclists.org
/fulldisclosure/2020/Feb/1
mailing-list
-
seclists.org
/bugtraq/2020/Feb/7
mailing-list
- packetstormsecurity.com /files/157528/HP-Performance-Monitoring-xglance-Privilege-Escalation.html
Sources
- CVE List CVE-2014-2630
- NVD CVE-2014-2630
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.