CyberSecBulletin
CVE-2022-38787NVD status: Modified

Improper input validation in firmware for some Intel(R) FPGA products before version 2.7.0…

Published Updated By the CyberSecBulletin desk

CVE-2022-38787 is a high-severity improper input validation vulnerability in Intel(R) FPGA products, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Intel(R) FPGA products versions: before version 2.7.0 Hotfix. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Intel(R) FPGA products you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on intel.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Intel(R) FPGA productsIntel(R) FPGA productsbefore version 2.7.0 HotfixNot stated
IntelAgilex 7 Fpga F-series 019 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 023 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 006 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 008 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 027 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 014 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 012 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga F-series 022 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 022 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 041 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 035 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 027 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 019 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 040 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga I-series 023 Firmware2.7.0 and earlierNot stated
IntelAgilex 7 Fpga M-series 039 Firmware2.7.0 and earlierNot stated
IntelStratix 10 Nx 2100 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Dx 2800 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Dx 2100 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Dx 1100 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Tx 1650 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Tx 2500 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Tx 2100 Fpga Firmware2.7.0 and earlierNot stated
IntelStratix 10 Tx 850 Fpga Firmware2.7.0 and earlierNot stated

Version data comes from the organisation that assigned the CVE; 24 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.15.7MediumCNA (intel.com)
CVSS 3.17.8HighNVD

Official description

Improper input validation in firmware for some Intel(R) FPGA products before version 2.7.0 Hotfix may allow an authenticated user to potentially enable escalation of privilege via local access.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Intel(R) FPGA products

All Intel(R) FPGA products vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.