Insufficient access control in system firmware for Intel(R) Xeon(R) Scalable Processors, 2nd Generation Intel(R) Xeon(R) Scalable Processors
Insufficient access control in system firmware for Intel(R) Xeon(R) Scalable Processors, 2nd Generation Intel(R) Xeon(R) Scalable Processors and Intel(R) Xeon(R) Processors D Family may allow a privileged user to potentially enable escalation of privilege, denial of service and/or information disclosure via local access.
- Published
- Nov 14, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 29th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| intel | xeon gold 6242 | cpe:2.3:h:intel:xeon_gold_6242 |
| intel | xeon gold 6154 | cpe:2.3:h:intel:xeon_gold_6154 |
| intel | xeon d-2141i | cpe:2.3:h:intel:xeon_d-2141i |
| intel | xeon platinum 8253 firmware | cpe:2.3:o:intel:xeon_platinum_8253_firmware |
| intel | xeon platinum 8253 | cpe:2.3:h:intel:xeon_platinum_8253 |
| intel | xeon platinum 8256 firmware | cpe:2.3:o:intel:xeon_platinum_8256_firmware |
| intel | xeon platinum 8256 | cpe:2.3:h:intel:xeon_platinum_8256 |
| intel | xeon platinum 8260 firmware | cpe:2.3:o:intel:xeon_platinum_8260_firmware |
| intel | xeon platinum 8260 | cpe:2.3:h:intel:xeon_platinum_8260 |
| intel | xeon platinum 8276 firmware | cpe:2.3:o:intel:xeon_platinum_8276_firmware |
| intel | xeon platinum 8276 | cpe:2.3:h:intel:xeon_platinum_8276 |
| intel | xeon platinum 8276m firmware | cpe:2.3:o:intel:xeon_platinum_8276m_firmware |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hpe apollo 4200 gen10 server firmwarebefore 2.20
- hpe apollo 4200 gen9 server firmwarebefore 2.76
- hpe proliant bl460c gen10 server blade firmwarebefore 2.20
- hpe proliant bl460c gen9 server blade firmwarebefore 2.76
- hpe proliant bl660c gen9 server firmwarebefore 2.76
- hpe proliant dl120 gen10 server firmwarebefore 2.20
- hpe proliant dl120 gen9 server firmwarebefore 2.76
- hpe proliant dl160 gen10 server firmwarebefore 2.20
- hpe proliant dl160 gen9 server firmwarebefore 2.76
- hpe proliant dl180 gen10 server firmwarebefore 2.20
- hpe proliant dl180 gen9 server firmwarebefore 2.76
- hpe proliant dl360 gen10 server firmwarebefore 2.20
- hpe proliant dl360 gen9 server firmwarebefore 2.76
- hpe proliant dl380 gen10 server firmwarebefore 2.20
- hpe proliant dl380 gen9 server firmwarebefore 2.76
- hpe proliant dl560 gen10 server firmwarebefore 2.20
- hpe proliant dl560 gen9 server firmwarebefore 2.76
- hpe proliant dl580 gen10 server firmwarebefore 2.20
- hpe proliant dl580 gen9 server firmwarebefore 2.76
- hpe proliant dl60 gen9 server firmwarebefore 2.76
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a 2019.2 IPU – UEFI
- See provided referenceaffected
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11137Insufficient input validation in system firmware for Intel(R) Xeon(R) Scalable Processors, Intel(R) Xeon(R) Processors D Family, Intel(R) Xe32Monitor
- CVE-2019-0152Insufficient memory protection in System Management Mode (SMM) and Intel(R) TXT for certain Intel(R) Xeon(R) Processors may allow a privileg26Monitor
- CVE-2022-26373Non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors may allow an authorized user to potentially22Monitor
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are 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
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- support.f5.com/csp/article/K56215245?utm_source=f5support&%3Butm_medium=RSS
- support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03967en_us
- www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00280.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.