CVE-2017-12653
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 · unedited360 Total Security 9.0.0.1202 before 2017-07-07 allows Privilege Escalation via a Trojan horse Shcore.dll file in any directory in the PATH, as demonstrated by the C:\Python27 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 360 Total Security where the application loads a malicious Shcore.dll file from any directory in the system PATH (demonstrated with C:\Python27). An attacker with local access can place a trojan horse DLL in a PATH directory, which gets loaded by the application, enabling privilege escalation.
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.0.0.1202CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Find installed 360 Total Security versionOpen Windows Settings > Apps & Features, or check Program Files for the 360 Total Security folder, or use 'wmic product get name,version' in command promptAffected if Version is 9.0.0.1202 or lower (the affected range is <= 9.0.0.1202)
-
Review system PATH directoriesRun 'echo %PATH%' in command prompt or view System Properties > Environment Variables > System variables > PathAffected if PATH contains directories with weak access controls such as C:\Python27, temporary folders, or user-writable directories that an unprivileged attacker could modify
-
Check for Shcore.dll in PATH directoriesSearch each PATH directory for the presence of Shcore.dll: use 'dir /s C:\Shcore.dll' or inspect each PATH folder manually for the fileAffected if Shcore.dll is found in any directory within the system PATH, indicating the vulnerable DLL loading could occur
-
Verify 360 Total Security executable locationLocate the main executable (usually in C:\Program Files\360\360TotalSecurity or C:\Program Files (x86)\360\360TotalSecurity) and note its PATH-relative loading behaviorAffected if The application loads DLLs from PATH directories instead of using secure absolute paths
If 360 Total Security version is 9.0.0.1202 or lower AND your system PATH contains writable directories where an attacker could place a malicious Shcore.dll, you are vulnerable to this DLL hijacking flaw.
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 360 Total Security to a version released after 2017-07-07 which contains the security fix. Alternatively, remove directories with weak access controls from the system PATH.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12653 — 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-2017-12653 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