CVE-2020-15722
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 version 12.1.0.1004 and below of 360 Total Security,when TPI calls the browser process, there exists a local privilege escalation vulnerability. An attacker who could exploit DLL hijacking 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 · moderate confidence360 Total Security versions 12.1.0.1004 and below contain a DLL hijacking vulnerability in the TPI component when calling browser processes. An attacker with local access could place a malicious DLL in a location where the vulnerable code would load it, achieving arbitrary code execution at SYSTEM privilege level.
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.1004CVSS 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 is installedCheck for the presence of 360 Total Security in the system. On Windows, look in Program Files or Program Files (x86) for a '360' folder, or check Add/Remove Programs. Registry key path: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\360 Total SecurityAffected if 360 Total Security software is found on the system
-
Identify installed version numberLocate the version information. Common paths: right-click the executable (usually tsafe.exe or 360Tray.exe in the install directory), select Properties, then Details tab. Also check registry: HKLM\SOFTWARE\360\Safe\Ver or look in the application's About/Help sectionAffected if The installed version is 12.1.0.1004 or any version lower than this (for example 12.0.x.x, 11.x.x.x)
-
Confirm TPI component is presentCheck for TPI-related files in the 360 Total Security installation directory. TPI is typically located in a subfolder related to browser protection or toolbar integration. Look for files with 'tpi' in the name or within a 'TPI' folderAffected if TPI component files exist in the 360 Total Security installation directory
-
Assess DLL search path accessibilityIdentify directories in the DLL search path used when the TPI component launches browser processes. Check if unprivileged users have write access to directories such as the application directory, system directories, or user-accessible paths where a malicious DLL could be placedAffected if Writable directories exist in the DLL search path accessible to unprivileged users that could be exploited for DLL hijacking
A user is affected if 360 Total Security version 12.1.0.1004 or lower is installed and the TPI browser call functionality is present with writable directories in the DLL 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 dataUpgrade 360 Total Security to a version newer than 12.1.0.1004 that addresses this vulnerability. As an interim measure, restrict write access to directories in the DLL search path used by the TPI browser call functionality.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15722 — 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-15722 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