CVE-2020-15724
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 · uneditedIn the version 12.1.0.1005 and below of 360 Total Security, when the Gamefolde calls GameChrome.exe, there exists a local privilege escalation vulnerability. An attacker who could exploit DLL hijacking to bypass the hips could execute arbitrary code on the Local system.
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 confidenceA DLL hijacking vulnerability exists in 360 Total Security versions 12.1.0.1005 and below where the Gamefolde component calls GameChrome.exe without secure DLL search order. An attacker with local access can place a malicious DLL in the search path, causing arbitrary code execution with elevated (SYSTEM) privileges, effectively bypassing the HIPS security control.
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<= 12.1.0.1005CVSS 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.1/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.
-
Verify 360 Total Security installationCheck for 360 Total Security in the system using installed programs list (Add/Remove Programs on Windows) or by searching for the executable in common installation directories.Affected if 360 Total Security is present on the system
-
Check installed version numberLocate the main executable (typically 360Tray.exe or similar) in the installation directory and check its version property, or use 'wmic product get name,version' command if available.Affected if The installed version is 12.1.0.1005 or lower
-
Locate Gamefolde componentSearch the 360 Total Security installation directory for folders or files named 'Gamefolde' or 'GameChrome' using file explorer search or command-line 'dir /s' within the program directory.Affected if A folder or executable named Gamefolde or GameChrome.exe exists in the 360 Total Security installation path
-
Verify vulnerable DLL search path conditionExamine the directory permissions on the GameChrome.exe parent folder and check if any directory in the DLL search order is writable by low-privileged users (run 'icacls' on the folder).Affected if The GameChrome.exe directory or any directory in the system DLL search path is writable by non-admin users, allowing placement of malicious DLLs
The system is affected if 360 Total Security version 12.1.0.1005 or lower is installed with the Gamefolde/GameChrome component present in a location where an attacker could place a malicious DLL in the search path.
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 dataThis is a vendor-side vulnerability requiring an update from 360 Security. The fix involves implementing secure DLL search order (Safe DLL Search Mode), using absolute paths for DLL loading, and/or implementing DLL integrity verification. Until the vendor releases a patch, restrict physical/logical access to the system and monitor for suspicious DLL loading activity.
- Consultation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15724 — 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-15724 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