CVE-2015-7333
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 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 INF and INF_BY_COMPATIBLE_ID command types 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 confidenceA local privilege escalation vulnerability exists in Lenovo System Update versions 5.07.0008 and prior. The SUService.exe component improperly handles /type INF and INF_BY_COMPATIBLE_ID command types, allowing an authenticated local user to execute arbitrary code with elevated (SYSTEM) privileges.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Lenovo System Update is installedLook for the Lenovo System Update installation directory (typically in Program Files) or check the installed programs list in Windows Control Panel. Also check for the SUService.exe process in Task Manager or via command: tasklist /FI "IMAGENAME eq SUService.exe"Affected if Lenovo System Update is found installed on the system
-
Determine the installed version of Lenovo System UpdateLocate the SUService.exe file (commonly in the Lenovo System Update installation folder, often under Program Files\Lenovo\System Update or similar). Right-click the file, select Properties, and check the Version tab for the file version. Alternatively, use command: wmic product where "name like 'Lenovo System Update'" get versionAffected if The version displayed is 5.07.0008 or any version prior to it (version number less than or equal to 5.07.0008)
-
Verify the SUService.exe component is presentCheck if SUService.exe exists on the system using File Explorer or command: dir /s /b C:\SUService.exe 2>nul (searches the entire C: drive) or check the specific installation directoryAffected if SUService.exe is found and its version cannot be determined or resolves to 5.07.0008 or prior
-
Confirm the service is configured to runCheck the SUService Windows service status using command: sc query SUService or through Services.msc. Also verify the service runs under a privileged accountAffected if The SUService is installed and runs with elevated privileges, and its version is <= 5.07.0008
The system is affected if Lenovo System Update with SUService.exe version 5.07.0008 or earlier is installed and the service component is present.
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. This vulnerability was fixed and publicly disclosed in 2015, so ensure all affected systems have applied the appropriate patch or update.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7333 — 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-7333 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