cve.bz

CVE-2019-11137 Improper Input Validation

8.2 highEPSS 0.4%

High (8.2). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Insufficient input validation in system firmware for Intel(R) Xeon(R) Scalable Processors, Intel(R) Xeon(R) Processors D Family, Intel(R) Xeon(R) Processors E5 v4 Family, Intel(R) Xeon(R) Processors E7 v4 Family and Intel(R) Atom(R) processor C Series may allow a privileged user to potentially enable escalation of privilege, denial of service and/or information disclosure via local access.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-11137 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-11137?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-11137?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-11137 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2019-11137

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2019-11137](https://cve.bz/cve/badge/CVE-2019-11137.svg)](https://cve.bz/cve/CVE-2019-11137)

HTML:

<a href="https://cve.bz/cve/CVE-2019-11137"><img src="https://cve.bz/cve/badge/CVE-2019-11137.svg" alt="CVE-2019-11137"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
hpe:apollo_4200_gen10_server_firmwarebefore 2.20
hpe:proliant_bl460c_gen10_server_blade_firmwarebefore 2.20
hpe:proliant_dl580_gen10_server_firmwarebefore 2.20
hpe:proliant_dl560_gen10_server_firmwarebefore 2.20
hpe:proliant_dl380_gen10_server_firmwarebefore 2.20
hpe:proliant_dl360_gen10_server_firmwarebefore 2.20
hpe:proliant_dl180_gen10_server_firmwarebefore 2.20
hpe:proliant_dl160_gen10_server_firmwarebefore 2.20
hpe:proliant_dl120_gen10_server_firmwarebefore 2.20
hpe:proliant_ml350_gen10_server_firmwarebefore 2.20
hpe:proliant_ml110_gen10_server_firmwarebefore 2.20
hpe:proliant_xl450_gen10_server_firmwarebefore 2.20
hpe:proliant_xl270d_gen10_server_firmwarebefore 2.20
hpe:proliant_xl230k_gen10_server_firmwarebefore 2.20
hpe:proliant_xl190r_gen10_server_firmwarebefore 2.20
hpe:proliant_xl170r_gen10_server_firmwarebefore 2.20
hpe:proliant_e910_server_blade_firmwarebefore 2.20
hpe:synergy_660_gen10_compute_module_firmwarebefore 2.20
hpe:synergy_480_gen10_compute_module_firmwarebefore 2.20
hpe:proliant_bl660c_gen9_server_firmwarebefore 2.76
hpe:proliant_bl460c_gen9_server_blade_firmwarebefore 2.76
hpe:proliant_dl580_gen9_server_firmwarebefore 2.76
hpe:proliant_dl560_gen9_server_firmwarebefore 2.76
hpe:proliant_dl380_gen9_server_firmwarebefore 2.76
hpe:proliant_dl360_gen9_server_firmwarebefore 2.76
hpe:proliant_dl180_gen9_server_firmwarebefore 2.76
hpe:proliant_dl160_gen9_server_firmwarebefore 2.76
hpe:proliant_dl120_gen9_server_firmwarebefore 2.76
hpe:proliant_dl80_gen9_server_firmwarebefore 2.76
hpe:proliant_dl60_gen9_server_firmwarebefore 2.76
hpe:proliant_xl730f_gen9_server_firmwarebefore 2.76
hpe:proliant_xl450_gen9_server_firmwarebefore 2.76
hpe:proliant_xl250a_gen9_server_firmwarebefore 2.76
hpe:proliant_xl230a_gen9_server_firmwarebefore 2.76
hpe:proliant_xl190r_gen9_server_firmwarebefore 2.76
hpe:proliant_xl170r_gen9_server_firmwarebefore 2.76
hpe:synergy_680_gen9_compute_module_firmwarebefore 2.76
hpe:synergy_620_gen9_compute_module_firmwarebefore 2.76
hpe:synergy_480_gen9_compute_module_firmwarebefore 2.76
hpe:proliant_ml150_gen9_server_firmwarebefore 2.76
hpe:proliant_ml110_gen9_server_firmwarebefore 2.76
hpe:apollo_4200_gen9_server_firmwarebefore 2.76
hpe:proliant_ml350_gen9_server_firmwarebefore 2.76
hpe:proliant_ws460c_gen9_graphics_server_blade_firmwarebefore 2.76

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON