CVE-2019-5245
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 · uneditedHiSuite 9.1.0.300 versions and earlier contains a DLL hijacking vulnerability. This vulnerability exists due to some DLL file is loaded by HiSuite improperly. And it allows an attacker to load this DLL file of the attacker's choosing that could execute arbitrary code.
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 confidenceHiSuite 9.1.0.300 and earlier versions contain a DLL hijacking vulnerability where the application improperly loads DLL files, allowing an attacker to place a malicious DLL in a location where HiSuite will load it, resulting in arbitrary code execution.
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<= 9.1.0.300CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 HiSuite is installedLook for HiSuite in the program files directory (typically C:\Program Files\Huawei\HiSuite or C:\Program Files (x86)\Huawei\HiSuite) or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Huawei HiSuiteAffected if HiSuite is present on the system
-
Identify installed HiSuite versionLocate the HiSuite executable (HiSuite.exe), right-click and select Properties, then check the Details tab for the Product Version; alternatively, check the uninstall registry entry for the DisplayVersion valueAffected if The installed version is 9.1.0.300 or earlier
-
Verify HiSuite installation directory permissionsRight-click the HiSuite installation folder, select Properties, go to the Security tab, and check if users without administrator privileges have Write or Modify permissionsAffected if Non-admin users have Write or Modify access to the HiSuite installation directory
-
Check PATH environment variable directoriesOpen System Properties > Advanced > Environment Variables, select the PATH variable under User or System variables, and verify each directory listed; for each directory, check folder permissions to see if unprivileged users have Write accessAffected if Any directory in the system or user PATH is writable by non-administrator users
You are affected if HiSuite is installed with version 9.1.0.300 or earlier AND either the HiSuite installation directory or any PATH directory is writable by unprivileged users, allowing an attacker to place a malicious DLL for the application to load.
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 dataApply the vendor patch or upgrade to a newer version of HiSuite that properly validates and loads DLL files using secure search order; alternatively, ensure the application directory and PATH locations are not writable by unprivileged users.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5245 — 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-2019-5245 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