CVE Intelligence
Medium Input validation

CVE-2020-8700 — Improper input validation in the firmware for some Intel(R) Processors may allow a privileged...

Improper input validation in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local access.

Published Jun 9, 2021 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: intel

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 21% of scored CVEs · Oct 14, 2026
Affects
Intel
Bios and 7 more
CVSS base
6.7
Medium · 2 source(s)

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.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

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 (Intel Bios, Netapp Aff Bios, Netapp Cloud Backup…).
  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.

VendorProductVersionsStatusSource
Intel Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Aff Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Cloud Backup versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp E-series Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Fas Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Compute Node Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Storage Node Bios versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire Bios versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

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

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
6.7 CVSS 3.1 Medium 0.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
6.7 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
4.6 CVSS 2.0 Medium 3.9 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

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.30%

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.
endpoint telemetry (EDR)

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 · 6.7
    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
  • 2021
  • CVE published
    Jun 9, 2021 · intel

Source activity

Repeated readings are counted rather than listed.

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

References

5 on the record

Elsewhere on this site

Intel
every CVE for this vendor
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2021-43975 Out-of-bounds Write in Linux Linux Kernel Nov 17, 2021
  • Critical CVE-2021-42013 Apache HTTP Server Path Traversal Vulnerability KEV Oct 7, 2021
  • Critical CVE-2021-41773 Apache HTTP Server Path Traversal Vulnerability KEV Oct 5, 2021
  • High CVE-2021-22946 A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking... Sep 29, 2021
  • Medium CVE-2021-22947 When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using... Sep 29, 2021
  • Critical CVE-2021-22945 When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances... Sep 23, 2021

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-2020-8700 is "Improper input validation in the firmware for some Intel(R) Processors may allow a privileged...", rated Medium. It affects Bios (Intel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.7 describes technical severity. EPSS 0.30% 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.