A local elevation of privilege using physical access security vulnerability was found in HPE Proliant Gen10 Servers using Intel Innovation E
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A local elevation of privilege using physical access security vulnerability was found in HPE Proliant Gen10 Servers using Intel Innovation Engine (IE). This attack requires a physical attack to the server motherboard. To mitigate this issue, ensure your server is always physically secured. HPE will not address this issue in the impacted Gen 10 servers listed. HPE recommends using appropriate physical security methods as a compensating control to disallow an attacker from having physical access to the server main circuit board.
- Published
- Nov 5, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- —
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hp | apollo 2000 firmware | cpe:2.3:o:hp:apollo_2000_firmware |
| hp | apollo 2000 | cpe:2.3:h:hp:apollo_2000 |
| hp | apollo 4200 gen10 firmware | cpe:2.3:o:hp:apollo_4200_gen10_firmware |
| hp | apollo 4200 gen10 | cpe:2.3:h:hp:apollo_4200_gen10 |
| hp | apollo 4500 firmware | cpe:2.3:o:hp:apollo_4500_firmware |
| hp | apollo 4500 | cpe:2.3:h:hp:apollo_4500 |
| hp | proliant xl230k gen10 firmware | cpe:2.3:o:hp:proliant_xl230k_gen10_firmware |
| hp | proliant xl230k gen10 | cpe:2.3:h:hp:proliant_xl230k_gen10 |
| hp | proliant xl270d gen10 firmware | cpe:2.3:o:hp:proliant_xl270d_gen10_firmware |
| hp | proliant xl270d gen10 | cpe:2.3:h:hp:proliant_xl270d_gen10 |
| hp | proliant bl460c gen10 firmware | cpe:2.3:o:hp:proliant_bl460c_gen10_firmware |
| hp | proliant bl460c gen10 | cpe:2.3:h:hp:proliant_bl460c_gen10 |
and 30 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp apollo 2000 firmwareall versions
- hp apollo 4200 gen10 firmwareall versions
- hp apollo 4500 firmwareall versions
- hp proliant bl460c gen10 firmwareall versions
- hp proliant dl120 gen10 firmwareall versions
- hp proliant dl160 gen10 firmwareall versions
- hp proliant dl180 gen10 firmwareall versions
- hp proliant dl360 gen10 firmwareall versions
- hp proliant dl380 gen10 firmwareall versions
- hp proliant dl560 gen10 firmwareall versions
- hp proliant dl580 gen10 firmwareall versions
- hp proliant e910 firmwareall versions
- hp proliant ml110 gen10 firmwareall versions
- hp proliant ml350 gen10 firmwareall versions
- hp proliant xl170r gen10 firmwareall versions
- hp proliant xl190r gen10 firmwareall versions
- hp proliant xl230k gen10 firmwareall versions
- hp proliant xl270d gen10 firmwareall versions
- hp proliant xl450 gen10 firmwareall versions
- hp synergy 480 gen10 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hpe). Independent of NVD's CPE analysis and usually ahead of it.
n/a HPE ProLiant BL460c Gen10 Server Blade; HPE ProLiant DL360 Gen10 Server; HPE ProLiant DL380 Gen10 Server; HPE ProLiant DL560 Gen10 Server; HPE ProLiant DL580 Gen10 Server; HPE ProLiant ML110 Gen10 Ser
- all current IE firmwareaffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.