CVE-2015-7335
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 · uneditedMITRE is populating this ID because it was assigned prior to Lenovo becoming a CNA. A race condition was reported (fixed and publicly disclosed in 2015) in Lenovo System Update version 5.07.0008 and prior that 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 · moderate confidenceA race condition in Lenovo System Update versions 5.07.0008 and prior allows a local attacker to execute arbitrary code with elevated privileges by exploiting a timing window during the update process.
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<= 5.07.0008CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Lenovo System Update is installedOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Lenovo*System*Update*"}' in PowerShell to find the installation entry.Affected if Lenovo System Update does not appear in the installed programs list, meaning it is not installed.
-
Locate the System Update executableIf installed, find the executable path. Common locations: C:\Program Files\Lenovo\System Update\SystemUpdate.exe or C:\Program Files (x86)\Lenovo\System Update\SystemUpdate.exe. Use 'Get-ChildItem -Path "C:\Program Files","C:\Program Files (x86)" -Recurse -Filter "SystemUpdate.exe" -ErrorAction SilentlyContinue' to locate it.Affected if The executable cannot be found in standard installation directories.
-
Retrieve the installed versionRight-click the SystemUpdate.exe file, select Properties, and view the 'File version' or 'Product version' field on the Details tab. Alternatively, run '(Get-Item "C:\Program Files\Lenovo\System Update\SystemUpdate.exe").VersionInfo' in PowerShell.Affected if The version cannot be determined or the file does not exist.
-
Compare version against the affected rangeCompare the retrieved version number to 5.07.0008. The affected version range is any version less than or equal to 5.07.0008. For example, versions like 5.07.0007, 5.06.0012, or 5.00.0000 are all within the affected range.Affected if The installed version is 5.07.0008 or any earlier version (e.g., 5.07.0007, 5.06.x, 5.05.x, etc.).
You are affected if Lenovo System Update is installed and the installed version is 5.07.0008 or any earlier version.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Lenovo System Update to a version newer than 5.07.0008, or apply the vendor-released patch. Verify the update in a test environment before production deployment.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7335 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7335 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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