dbcve.org
Ideacentre Aio 3 21itl7 FirmwareOperating system · Lenovo

CVE-2022-48188

HIGH · 7.8 CVSS v3.1 Published 2023-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer overflow vulnerability exists in the SecureBootDXE BIOS driver on certain Lenovo Desktop and ThinkStation systems. The flaw allows a local attacker with physical access to trigger the overflow and elevate privileges to execute arbitrary code, likely within System Management Mode (SMM) or a similarly privileged execution context.

MitigationApply the Lenovo BIOS firmware update for affected models when released. Until patched, restrict physical access to vulnerable systems and verify Secure Boot is properly enabled as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ideacentre Aio 3 21itl7 FirmwareOperating system
Affected:< o5akt33
Ideacentre Aio 3 22itl6 FirmwareOperating system
Affected:< o5akt33
Ideacentre Aio 3 24itl6 FirmwareOperating system
Affected:< o5akt33
Ideacentre Aio 3 27itl6 FirmwareOperating system
Affected:< o5akt33
Thinkcentre M720e FirmwareOperating system
Affected:< m1zkt40a
Thinkcentre M720q FirmwareOperating system
Affected:< m1ukt70a
Thinkcentre M720s FirmwareOperating system
Affected:< m1ukt70a
Thinkcentre M720t FirmwareOperating system
Affected:< m1ukt70a

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the exact system model
    Check the system model number on the chassis or via command: `wmic computersystem get model` on Windows or `sudo dmidecode -s system-product-name` on Linux
    Affected if The model is not one of: Ideacentre Aio 3 21itl7, Ideacentre Aio 3 22itl6, Ideacentre Aio 3 24itl6, Ideacentre Aio 3 27itl6, Thinkcentre M720e, Thinkcentre M720q, Thinkcentre M720s, or Thinkcentre M720t - if so, this CVE does not apply
  2. Determine the installed BIOS firmware version
    Use Lenovo Vantage, System Update, or `wmic bios get smbiosbiosversion` on Windows; `sudo dmidecode -s bios-version` on Linux; or check the BIOS setup utility under the Version or Update section
    Affected if Unable to retrieve a firmware version string from the system BIOS/UEFI
  3. Compare firmware version against affected ranges for Ideacentre Aio 3
    If the system is an Ideacentre Aio 3 model (21itl7, 22itl6, 24itl6, or 27itl6), compare the installed version to o5akt33 - versions below o5akt33 are affected
    Affected if The installed version string is lexicographically less than o5akt33 (e.g., o5akt32, o5akt30, etc.)
  4. Compare firmware version against affected ranges for Thinkcentre M720e
    If the system is a Thinkcentre M720e, compare the installed version to m1zkt40a - versions below m1zkt40a are affected
    Affected if The installed version string is lexicographically less than m1zkt40a
  5. Compare firmware version against affected ranges for Thinkcentre M720q/s/t
    If the system is a Thinkcentre M720q, M720s, or M720t, compare the installed version to m1ukt70a - versions below m1ukt70a are affected
    Affected if The installed version string is lexicographically less than m1ukt70a

The system is affected only if it is one of the eight listed models AND its BIOS firmware version is below the corresponding threshold (o5akt33, m1zkt40a, or m1ukt70a); otherwise, it is not vulnerable to this specific CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Lenovo BIOS firmware update for affected models when released. Until patched, restrict physical access to vulnerable systems and verify Secure Boot is properly enabled as a compensating control.

Recommended fix Moderate confidence

Ideacentre Aio 3 series: firmware o5akt33 or later | Thinkcentre M720e: firmware m1zkt40a or later | Thinkcentre M720q/M720s/M720t: firmware m1ukt70a or later

  1. Identify your exact model number and hardware version from the system label or BIOS information
  2. Navigate to support.lenovo.com and enter your model number to find the BIOS/firmware download page
  3. Download the appropriate BIOS update package for your specific model
  4. Review the update instructions included with the download
  5. Run the BIOS update utility following Lenovo's documented process, or create a bootable USB update media if required
  6. Ensure the system is connected to stable power throughout the update process - do not interrupt the update
Caveat BIOS firmware updates carry a risk of rendering the system unusable if interrupted or if the wrong version is applied; ensure you select the exact model matching your hardware

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ideacentre Aio 3 21itl7 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-48188 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data