CVE-2015-8536
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 vulnerability was discovered (fixed and publicly disclosed in 2015) in Lenovo Solution Center (LSC) prior to version 3.3.002 that could allow cross-site request forgery.
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 cross-site request forgery (CSRF) vulnerability in Lenovo Solution Center (LSC) versions prior to 3.3.002 could allow remote attackers to trick authenticated users into executing unintended actions by embedding malicious requests in web pages or emails.
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< 3.3.002CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm Lenovo Solution Center is installedCheck for Lenovo Solution Center in the Windows Start Menu, or look for the application in Programs and Features (Add/Remove Programs). The application is typically installed under C:\Program Files\Lenovo\ or C:\Program Files (x86)\Lenovo\Affected if The application is present on the system
-
Identify the installed version numberRight-click the Lenovo Solution Center shortcut, select Properties, and check the 'Details' tab for the version information. Alternatively, open the Windows Control Panel, find Lenovo Solution Center in the Programs list, and view the version column.Affected if The version shown is earlier than 3.3.002 (for example, 3.3.000, 3.2.x, or earlier)
-
Verify the LSC web service is accessibleOpen a web browser and attempt to access the local Lenovo Solution Center web interface, typically at http://localhost:port or http://127.0.0.1:port (the specific port varies by installation). Check if the LSC dashboard loads.Affected if The web interface loads and the user can authenticate to it, meaning the CSRF attack surface is present
-
Cross-reference version with official advisoryVisit the Lenovo support website or security advisory database and confirm the version 3.3.002 contains the CSRF fix referenced in CVE-2015-8536.Affected if The installed version is confirmed to be before 3.3.002 and the advisory matches this range
If Lenovo Solution Center is installed and the version is below 3.3.002 with the web interface accessible, the environment is affected by this CSRF vulnerability.
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 data3.3.002
Upgrade Lenovo Solution Center to version 3.3.002 or later to obtain the vendor-supplied CSRF fix.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8536 — 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-8536 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