CVE-2016-2780
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 · uneditedUntrusted search path vulnerability in Huawei UTPS before UTPS-V200R003B015D15SP00C983 allows local users to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse DLL in an unspecified directory.
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 confidenceThis is a DLL hijacking vulnerability in Huawei UTPS (a terminal/connectivity product). The application loads dynamic-link libraries from untrusted search paths, allowing local attackers to place a malicious DLL in an unspecified directory that the application will load, resulting in arbitrary code execution with the privileges of the running user.
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= 23.009.09.00.983CVSS 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.0/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.
-
Confirm Huawei UTPS installationSearch for UTPS-related executables or check Program Files directories for Huawei UTPS folder, or look for UTPS service/process on the systemAffected if Huawei UTPS software is present on the system
-
Identify installed UTPS versionLocate the main UTPS executable (typically utps.exe or similar), right-click and select Properties, or use command 'wmic product get name,version' if listed as installed software, or check version info via the executableAffected if Version displayed matches exactly 23.009.09.00.983
-
Verify exact version matchCompare the identified version number to the affected version 23.009.09.00.983 - note this is an exact version match (equals), not a rangeAffected if Installed version is 23.009.09.00.983 exactly
-
Assess DLL search path exposureCheck if any user-writable directories (such as temporary folders, user profile directories, or network shares) exist in system PATH or are accessible to the UTPS application process at runtime - examine the system PATH variable and any custom paths UTPS may useAffected if User-writable directories are present in paths where UTPS loads DLLs from
You are affected if Huawei UTPS version 23.009.09.00.983 is installed AND user-writable directories exist in locations where the application searches for DLLs.
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 dataUpdate to Huawei UTPS version V200R003B015D15SP00C983 or later. Alternatively, ensure the application runs from a secure directory and remove any user-writable directories from the system DLL search path.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2780 — 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-2016-2780 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