CVE-2020-8357
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 · uneditedA denial of service vulnerability was reported in Lenovo PCManager, prior to version 3.0.200.2042, that could allow configuration files to be written to non-standard locations.
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 confidenceLenovo PCManager prior to version 3.0.200.2042 contains a path traversal vulnerability allowing configuration files to be written to arbitrary locations outside the intended directory, which can be exploited to cause denial of service by filling disk space or corrupting application state.
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.0.200.2042CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 PCManager is installedLook for Lenovo PCManager in the system. Common installation paths: C:\Program Files\Lenovo\Lenovo Vantage\ or C:\Program Files\Lenovo\Lenovo PC Manager\. Also check Add/Remove Programs or Programs and Features in Control Panel for 'Lenovo PCManager' or 'Lenovo Vantage'.Affected if Lenovo PCManager is found on the system
-
Determine the installed version of Lenovo PCManagerIf found, locate the version information. Check the executable properties (right-click on the .exe file, go to Details tab) or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for Lenovo PCManager entry, or look in the application's installation folder for a version file.Affected if The version cannot be determined or is lower than 3.0.200.2042
-
Compare installed version against the affected rangeIf version is obtained, compare it numerically to 3.0.200.2042. Version numbers follow format Major.Minor.Build.Revision. Any version below 3.0.200.2042 (such as 3.0.200.2041, 3.0.200, 3.0.0, or earlier) is within the affected range.Affected if Installed version is less than 3.0.200.2042
-
Verify if the application has write access to configuration filesThe vulnerability is exploitable when the application writes configuration files. Check if the application has been run and if configuration files exist in user-accessible directories. Inspect %APPDATA%\Lenovo\ or %LOCALAPPDATA%\Lenovo\ for PCManager folders.Affected if Configuration files exist and the vulnerable version is installed
The system is affected if Lenovo PCManager is installed with a version lower than 3.0.200.2042 and the application has been used to create configuration files.
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.0.200.2042
Update Lenovo PCManager to version 3.0.200.2042 or later. Verify that no unauthorized configuration files exist in unexpected filesystem locations.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8357 — 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-2020-8357 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