System UpdateApplication · Lenovo

CVE-2015-7334

HIGH · 7.8 CVSS v3.1 Published 2020-03-27
Fix available
A fix is available. Upgrade to after 5.07.0008 or later.
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
MITRE is populating this ID because it was assigned prior to Lenovo becoming a CNA. A local privilege escalation vulnerability was reported (fixed and publicly disclosed in 2015) in Lenovo System Update version 5.07.0008 and prior where the SUService.exe /type COMMAND type could allow a user to execute arbitrary code with elevated 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 · high confidence

A local privilege escalation vulnerability in Lenovo System Update version 5.07.0008 and prior allows local users to execute arbitrary code with elevated privileges via the SUService.exe service when invoked with the /type COMMAND parameter. The service improperly validates or does not properly restrict the command execution, enabling a low-privilege user to gain SYSTEM-level access.

MitigationUpdate Lenovo System Update to a version newer than 5.07.0008. As this is a local privilege escalation, ensure proper access controls and monitor for unauthorized access to the affected system.

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.07.0008

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. Check if Lenovo System Update is installed
    Open Windows Control Panel, go to Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Lenovo System Update*"}' in PowerShell
    Affected if Lenovo System Update appears in the installed programs list
  2. Determine the installed version of Lenovo System Update
    In Programs and Features, locate Lenovo System Update and note the version column, or check the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\DisplayVersion
    Affected if The version listed is 5.07.0008 or any version lower than 5.07.0008
  3. Locate the SUService.exe file
    Search for SUService.exe in typical installation paths such as C:\Program Files\Lenovo\System Update\ or C:\Program Files (x86)\Lenovo\System Update\, or use 'Get-ChildItem -Path "C:\Program Files" -Recurse -Filter "SUService.exe" -ErrorAction SilentlyContinue'
    Affected if SUService.exe exists in a Lenovo System Update directory
  4. Verify the SUService.exe version
    Right-click the SUService.exe file, go to Properties, and check the Details tab for the File Version, or run 'Get-Item "path\to\SUService.exe" | Select-Object VersionInfo | Format-List *'
    Affected if The file version is 5.07.0008 or lower
  5. Check if the SUService service is running
    Open Services (services.msc), locate 'Lenovo System Update Service' or 'SUService', and check its Status, or run 'Get-Service -Name *Lenovo* -ErrorAction SilentlyContinue' in PowerShell
    Affected if The service is installed and running with SYSTEM or elevated privileges

Your environment is affected if Lenovo System Update version 5.07.0008 or lower is installed and the SUService.exe service is present and executable by a low-privilege user.

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.

From vendor data
Upgrade available Upgrade to a release after 5.07.0008
Interim mitigation

Update Lenovo System Update to a version newer than 5.07.0008. As this is a local privilege escalation, ensure proper access controls and monitor for unauthorized access to the affected system.

Fix this in System Update Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2015-7334 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