CyberSecBulletin
CVE-2022-48188NVD status: Modified

ThinkStation BIOS: Out-of-bounds Write

CVE-2022-48188 is a high-severity out-of-bounds write vulnerability in ThinkStation BIOS from Lenovo, 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 ThinkStation BIOS versions: various. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.19% 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 Ideacentre Aio 3 21itl7 Firmware to o5akt33 or a later version.
  2. Update Ideacentre Aio 3-22itl6 Firmware to o5akt33 or a later version.
  3. Update Ideacentre Aio 3-24itl6 Firmware to o5akt33 or a later version.
  4. Read the advisory on support.lenovo.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
LenovoThinkStation BIOSvariousNot stated
LenovoIdeacentre Aio 3 21itl7 Firmwarebefore o5akt33o5akt33
LenovoIdeacentre Aio 3-22itl6 Firmwarebefore o5akt33o5akt33
LenovoIdeacentre Aio 3-24itl6 Firmwarebefore o5akt33o5akt33
LenovoIdeacentre Aio 3-27itl6 Firmwarebefore o5akt33o5akt33
LenovoThinkcentre M720e Firmwarebefore m1zkt40am1zkt40a
LenovoThinkcentre M720q Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M720s Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M720t Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M725s Firmwarebefore m25kt63am25kt63a
LenovoThinkcentre M75s Gen 2 Firmwarebefore m46kt30a; before m3bkt30am46kt30a, m3bkt30a
LenovoThinkcentre M75t Gen 2 Firmwarebefore m46kt30a; before m3akt4cam46kt30a, m3akt4ca
LenovoThinkcentre M920q Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M920s Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M920t Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M920x Firmwarebefore m1ukt70am1ukt70a
LenovoThinkcentre M920z Firmwarebefore m1mkt55am1mkt55a
LenovoIdeacentre 510s-07icb Firmwarebefore m22kt48a; before m22kt49am22kt48a, m22kt49a
LenovoIdeacentre 510s-07ick Firmwarebefore m30kt28a; before m1zkt40am30kt28a, m1zkt40a
LenovoIdeacentre 720-18apr Firmwarebefore m25kt63am25kt63a
LenovoV30a-22itl Firmwarebefore o5akt33o5akt33
LenovoV30a-24itl Firmwarebefore o5akt33o5akt33
LenovoV530s-07icb Firmwarebefore m22kt49am22kt49a
LenovoV530s-07icr Firmwarebefore m1zkt40am1zkt40a
LenovoThinkstation P330 Tiny Firmwarebefore m1ukt70am1ukt70a

Version data comes from the organisation that assigned the CVE; 3 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.16.7MediumCNA (lenovo.com)
CVSS 3.17.8HighNVD

Official description

A buffer overflow vulnerability in the SecureBootDXE BIOS driver of some Lenovo Desktop and ThinkStation models could allow an attacker with local access to elevate their privileges to execute arbitrary code.

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

Other vulnerabilities in ThinkStation BIOS

All ThinkStation BIOS vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.