CVE-2020-1817
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 · uneditedHuawei PCManager with versions earlier than 10.0.1.36 has a privilege escalation vulnerability. Due to improper permission management of specific files, local attackers with low permissions can inject commands to exploit this vulnerability. Successful exploit may cause privilege escalation.
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 confidenceHuawei PCManager versions before 10.0.1.36 contain improperly secured files with weak permission controls, allowing low-privilege local users to inject executable commands into these files and escalate to elevated 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< 10.0.1.36CVSS 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.
-
Check if Huawei PCManager is installedOpen Windows Settings > Apps & features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*PCManager*"}' in PowerShellAffected if Huawei PCManager appears in the installed programs list
-
Determine the installed PCManager versionRun 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*PCManager*"} | Select-Object Name, Version' in PowerShell, or check the version from the application's About/Help sectionAffected if The displayed version number is lower than 10.0.1.36 (e.g., 10.0.0.x, 9.x.x.x)
-
Locate PCManager installation directoriesCheck common installation paths: C:\Program Files\Huawei\PCManager\ or C:\Program Files (x86)\Huawei\PCManager\, or find via 'Get-ChildItem -Path "C:\Program Files" -Recurse -Filter "PCManager*" -ErrorAction SilentlyContinue'Affected if PCManager installation folders exist on the system
-
Inspect file permissions for weak access controlsRight-click on files within the PCManager folder (especially executable files, .dll, .exe, .config files), select Properties > Security, and verify if Users or Everyone group has Write or Modify permissions. Alternatively, run 'icacls "C:\Program Files\Huawei\PCManager\*"' in Command PromptAffected if Files or folders show permissions granting Write/Modify access to Users, Everyone, or Authenticated Users groups (weak permissions)
-
Verify executable file integrityExamine key executable files in the PCManager directory (e.g., PCManager.exe, service-related .exe files) to see if they can be replaced by a low-privilege user. Attempt to rename or delete a sample file using a standard user accountAffected if Low-privilege accounts can modify, replace, or write to executable files used by PCManager services
A system is affected if Huawei PCManager version is below 10.0.1.36 AND the installation directory contains files with weak permissions allowing standard users to write or modify executable 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 data10.0.1.36
Upgrade Huawei PCManager to version 10.0.1.36 or later to obtain the patched file permission controls.
- 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-2020-1817 — 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-1817 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