LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33975: Buffer Overflow vulnerability in Qihoo 360 Total Security v10.8.0.1060 and v10.8.0.1213 allows attacker to...

Buffer Overflow vulnerability in Qihoo 360 Total Security v10.8.0.1060 and v10.8.0.1213 allows attacker to escalate privileges.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-33975 is reported as a critical buffer overflow in Qihoo 360 Total Security versions 10.8.0.1060 and 10.8.0.1213. The reported impact is privilege escalation, meaning an attacker could gain higher control on affected systems. The source bundle does not name a vendor patch or confirmed active exploitation.

Executive priority

Treat this as urgent for environments using the named versions, but first validate presence. The critical CVSS score and no-auth, no-user-interaction vector justify rapid triage; incomplete vendor and fix evidence means remediation should be anchored to current vendor guidance.

Technical view

The CVE describes CWE-120 buffer overflow behavior with CVSS 3.1 score 10.0 and vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Although the title names Qihoo 360 Total Security versions 10.8.0.1060 and 10.8.0.1213, the structured affected field lacks vendor, product, version, and CPE detail.

Likely exposure

Exposure is most likely limited to systems running the named Qihoo 360 Total Security versions. Asset confirmation is important because the structured affected metadata is incomplete and provides no CPEs or platform scope.

Exploitation context

The source bundle does not show CISA KEV listing or any cited confirmation of active exploitation. Public references exist, but the bundle does not establish weaponization, exploit maturity, or vendor-confirmed attack activity.

Researcher notes

Key gaps are affected-platform precision, CPEs, vendor advisory status, and confirmed remediation. The CVSS vector indicates severe remote attack characteristics, while the description frames the impact as privilege escalation. Avoid assuming active exploitation because KEV is false and the provided sources do not confirm it.

Mitigation direction

  • Identify any systems running Qihoo 360 Total Security 10.8.0.1060 or 10.8.0.1213.
  • Check Qihoo 360 vendor guidance for fixed versions or official mitigation advice.
  • Upgrade, remove, or isolate affected installations if vendor guidance confirms exposure.
  • Limit network exposure to affected hosts where operationally feasible.
  • Prioritize monitoring for unusual privilege changes on systems with the product installed.

Validation and detection

  • Query endpoint inventory for the exact named product versions.
  • Confirm findings manually on representative hosts where inventory is uncertain.
  • Review vendor advisories before declaring a patched or unaffected state.
  • Check EDR and system logs for suspicious privilege escalation activity.
  • Track whether CVE or vendor records add affected CPEs or remediation details.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-33975 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2021-33975Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.