dbcve.org
System UpdateApplication · Lenovo

CVE-2022-4568

HIGH · 7.0 CVSS v3.1 Published 2023-05-01
Fix available
A fix is available. Upgrade to 5.08.01.0005 or later.
See remediation →
72/100
Remediation priority · Elevated
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 directory permissions management vulnerability in Lenovo System Update may allow elevation of privileges.

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 · moderate confidence

A directory permissions management vulnerability in Lenovo System Update allows an authenticated attacker to manipulate directory permissions to gain elevated privileges on the system.

MitigationApply the vendor patch from Lenovo for System Update; verify the updated version properly secures directory permissions.

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
System UpdateApplication
Affected:< 5.08.01.0005

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Check if Lenovo System Update is installed
    Locate Lenovo System Update on the system - common paths include C:\Program Files\Lenovo\System Update or check Windows Registry under HKLM\SOFTWARE\Lenovo\SystemUpdate or HKLM\SOFTWARE\WOW6432Node\Lenovo\SystemUpdate
    Affected if Lenovo System Update is not found on the system - the user is not affected by this vulnerability
  2. Identify the installed version of Lenovo System Update
    Right-click the TVSU.exe file in the installation directory, select Properties, then view the Details tab for the Product Version field. Alternatively, check the Windows Registry value 'Version' under the SystemUpdate registry key
    Affected if The installed version is lower than 5.08.01.0005 - the user is affected
  3. Verify directory permissions on the System Update installation folder
    Right-click the Lenovo System Update installation folder, select Properties, then navigate to the Security tab. Verify that standard user accounts cannot modify folders or files within the installation directory, particularly the 'TVSU' subfolder and any 'Config' or 'Data' subdirectories
    Affected if Non-admin users have write or modify permissions to System Update directories that should be restricted - the user is affected even if version is unknown or appears patched
  4. Check for unauthorized permission modifications
    Review the permissions on the System Update installation directory and compare against expected defaults. Use 'icacls' command (e.g., icacls "C:\Program Files\Lenovo\System Update") to list effective permissions for standard users
    Affected if Authenticated users or non-admin accounts have elevated permissions allowing directory modification or ownership changes - the user is affected

The user is affected if Lenovo System Update is installed with a version lower than 5.08.01.0005 OR if non-administrative users have elevated directory permissions on the System Update installation folders.

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
Upgrade available Upgrade to 5.08.01.0005 or later
Fixed in 5.08.01.0005
Interim mitigation

Apply the vendor patch from Lenovo for System Update; verify the updated version properly secures directory permissions.

Recommended fix Moderate confidence

5.08.01.0005 or later

  1. Download Lenovo System Update version 5.08.01.0005 or later from the official Lenovo support website
  2. Install the updated Lenovo System Update application
  3. Restart the system if prompted to complete the installation
  4. Verify the installed version matches or exceeds 5.08.01.0005

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

Fix this in System Update Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4568 — 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-4568 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