dbcve.org
Safe BrowserApplication · Browser.360

CVE-2021-33975

CRITICAL · 10.0 CVSS v3.1 Published 2023-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
Buffer Overflow vulnerability in Qihoo 360 Total Security v10.8.0.1060 and v10.8.0.1213 allows attacker to escalate privileges.

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 confidence

Buffer overflow vulnerability in Qihoo 360 Total Security versions 10.8.0.1060 and 10.8.0.1213 allows attackers to execute arbitrary code with elevated privileges, potentially achieving full system compromise.

MitigationUpdate to the latest patched version of 360 Total Security or apply vendor-supplied security patches to remediate the buffer overflow vulnerability.

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
Safe BrowserApplication
Affected:= 13.0.2170.0

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if 360 Safe Browser is installed
    Check your system for the presence of 360 Safe Browser application - look in your installed programs list or program files directory for any application named '360 Safe Browser' or '360 Secure Browser'
    Affected if 360 Safe Browser is found on the system
  2. Determine the installed version of 360 Safe Browser
    Access the version information for the installed 360 Safe Browser - this is typically found in the program's properties, about section, or help menu within the browser itself
    Affected if The version displayed is exactly 13.0.2170.0
  3. Compare your version to the affected range
    Take the version number you found and compare it directly to the affected version 13.0.2170.0 - exact match indicates the specific version affected by this CVE
    Affected if Your installed version is exactly 13.0.2170.0

If 360 Safe Browser version 13.0.2170.0 is installed, your environment matches the affected version listed in this CVE and may be vulnerable to the buffer overflow that could allow privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of 360 Total Security or apply vendor-supplied security patches to remediate the buffer overflow vulnerability.

Fix this in Safe Browser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA3.0 h
12.0 hours of engineering $2,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33975 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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