CVE-2019-11137 — Improper Input Validation in Hpe Apollo 4200 Gen10 Server Firmware

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Hpe Apollo 4200 Gen10 Server Firmware, Hpe Apollo 4200 Gen9 Server Firmware, Hpe Proliant Bl460c Gen10 Server Blade Firmware…).
2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
3. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.38%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 8.2
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Modified
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• 2019
• CVE published
  Nov 14, 2019 · intel

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

• www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00280.html
  Vendor Advisory, x_refsource_MISC, NIST National Vulnerability Database
• support.f5.com/csp/article/K56215245
  x_refsource_CONFIRM, NIST National Vulnerability Database
• support.hpe.com/hpsc/doc/public/display
  Third Party Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2022-26373 Non-transparent sharing of return predictor targets between contexts in some Intel(R) Processors... Aug 18, 2022
• Medium CVE-2019-11136 Insufficient access control in system firmware for Intel(R) Xeon(R) Scalable Processors… Nov 14, 2019

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-11137 is "Improper Input Validation in Hpe Apollo 4200 Gen10 Server Firmware", rated High. It affects Apollo 4200 Gen10 Server Firmware (Hpe); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. EPSS 0.38% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.