CyberSecBulletin
CVE-2022-29277NVD status: Modified

Genoa Firmware: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-29277 is a high-severity out-of-bounds write vulnerability in Genoa Firmware from AMD, with a CVSS 3.1 base score of 8.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. The record lists version 05.52.25.0006 as the first without the flaw, so updating Genoa Firmware to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% 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. Update Genoa Firmware to 05.52.25.0006 or a later version.
  2. Update Hygon 1 Firmware to 05.36.26.0016 or a later version.
  3. Update Hygon 2 Firmware to 05.36.26.0016 or a later version.
  4. Read the advisory on insyde.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
AMDGenoa Firmwarebefore 05.52.25.000605.52.25.0006
AMDHygon 1 Firmwarebefore 05.36.26.001605.36.26.0016
AMDHygon 2 Firmwarebefore 05.36.26.001605.36.26.0016
AMDHygon 3 Firmwarebefore 05.44.26.000705.44.26.0007
AMDMilan Firmwarebefore 05.36.10.0017; before 05.36.26.001605.36.10.0017, 05.36.26.0016
AMDRome Firmwarebefore 05.36.10.0017; before 05.36.26.001605.36.10.0017, 05.36.26.0016
AMDRyzen 5300g Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5300ge Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5600g Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5600ge Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5600x Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5700g Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5700ge Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5800x Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5800x3d Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5900x Firmwarebefore 05.44.30.000405.44.30.0004
AMDRyzen 5950x Firmwarebefore 05.44.30.000405.44.30.0004
AMDSnowy Owl R1000 Firmwarebefore 05.32.50.001805.32.50.0018
AMDSnowy Owl R2000 Firmwarebefore 05.44.30.000505.44.30.0005
AMDSnowy Owl V2000 Firmwarebefore 05.44.30.000705.44.30.0007
AMDSnowy Owl V3000 Firmwarebefore 05.44.30.000705.44.30.0007
IntelAlder Lake Firmwarebefore 05.44.23.004705.44.23.0047
IntelBakerville Firmwarebefore 05.21.51.002605.21.51.0026
IntelCedar Island Firmwarebefore 05.42.11.002105.42.11.0021
IntelIdaville Firmwarebefore 05.43.12.005205.43.12.0052

Version data comes from NVD's product matching; 14 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
ChangedThe attack can reach beyond the vulnerable component into other systems.
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:C/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighNVD
CVSS 3.18.8HighCISA (ADP)

Official description

Incorrect pointer checks within the the FwBlockServiceSmm driver can allow arbitrary RAM modifications During review of the FwBlockServiceSmm driver, certain instances of SpiAccessLib could be tricked into writing 0xff to arbitrary system and SMRAM addresses. Fixed in: INTEL Purley-R: 05.21.51.0048 Whitley: 05.42.23.0066 Cedar Island: 05.42.11.0021 Eagle Stream: 05.44.25.0052 Greenlow/Greenlow-R(skylake/kabylake): Trunk Mehlow/Mehlow-R (CoffeeLake-S): Trunk Tatlow (RKL-S): Trunk Denverton: 05.10.12.0042 Snow Ridge: Trunk Graneville DE: 05.05.15.0038 Grangeville DE NS: 05.27.26.0023 Bakerville: 05.21.51.0026 Idaville: 05.44.27.0030 Whiskey Lake: Trunk Comet Lake-S: Trunk Tiger Lake H/UP3: 05.43.12.0052 Alder Lake: 05.44.23.0047 Gemini Lake: Not Affected Apollo Lake: Not Affected Elkhart Lake: 05.44.30.0018 AMD ROME: trunk MILAN: 05.36.10.0017 GENOA: 05.52.25.0006 Snowy Owl: Trunk R1000: 05.32.50.0018 R2000: 05.44.30.0005 V2000: Trunk V3000: 05.44.30.0007 Ryzen 5000: 05.44.30.0004 Embedded ROME: Trunk Embedded MILAN: Trunk Hygon Hygon #1/#2: 05.36.26.0016 Hygon #3: 05.44.26.0007 https://www.insyde.com/security-pledge/SA-2022060

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

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

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

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.