PcmanagerApplication · Huawei

CVE-2019-5242

HIGH · 7.8 CVSS v3.0 Published 2019-06-06
Fix available
A fix is available. Upgrade to after 9.0.1.50 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
There is a code execution vulnerability in Huawei PCManager versions earlier than PCManager 9.0.1.50. The attacker can tricking a user to install and run a malicious application to exploit this vulnerability. Successful exploitation may cause the attacker to execute malicious code and read/write memory.

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 confidence

Huawei PCManager versions before 9.0.1.50 contain a code execution vulnerability that allows a local attacker to execute malicious code and read/write memory by tricking a user into installing and running a malicious application. The vulnerability likely involves improper validation of code executed by the PCManager service.

MitigationUpdate Huawei PCManager to version 9.0.1.50 or later. Until patched, restrict user permissions and monitor for unauthorized or suspicious applications being executed.

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
PcmanagerApplication
Affected:<= 9.0.1.50

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Huawei PCManager is installed
    Search for PCManager installation directory, typically in C:\Program Files\Huawei\PCManager or C:\Program Files (x86)\Huawei\PCManager. Also check Add/Remove Programs for Huawei PCManager.
    Affected if Huawei PCManager is found installed on the system
  2. Identify installed PCManager version
    Locate the PCManager executable (PCManager.exe) or check the version through the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PCManager or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\PCManager. Right-click the executable, select Properties, and view the Details tab for version information.
    Affected if The installed version is 9.0.1.50 or lower, or no version is displayed (indicating an old install)
  3. Verify PCManager service or process is running
    Open Task Manager or run 'sc query PCManager' from command prompt to check if the PCManager service is active. The vulnerability involves code execution by the PCManager service, so an active service is required for exploitation.
    Affected if PCManager service or process is currently running on the system
  4. Inspect running processes for unauthorized applications
    Review running processes in Task Manager, particularly looking for unknown or suspicious applications that may have been executed through the PCManager service vulnerability. Check for any unexpected processes spawning from PCManager directories.
    Affected if Unknown or malicious-looking processes are observed running alongside or spawned by PCManager

If Huawei PCManager version 9.0.1.50 or lower is installed and the service is running, the system is potentially affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 9.0.1.50
Interim mitigation

Update Huawei PCManager to version 9.0.1.50 or later. Until patched, restrict user permissions and monitor for unauthorized or suspicious applications being executed.

Fix this in Pcmanager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5242 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5242 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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