# CVE-2021-33971: Memory corruption in n/a > Attackers can execute arbitrary code and escalate privileges via buffer overflows in Qihoo 360 security software, potentially bypassing antivirus protections. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 19 Apr 2023 - **Updated:** 5 Feb 2025 - **Also known as:** GHSA-qcrm-cg47-3qvc ## What is CVE-2021-33971? CVE-2021-33971 is a high-severity memory corruption vulnerability in n/a, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Qihoo 360 (https://www.360.cn/) Qihoo 360 Safeguard (https://www.360.cn/) Qihoo 360 Total Security (http://www.360totalsecurity.com/) is affected by: Buffer Overflow. The impact is: execute arbitrary code (local). The component is: This is a set of vulnerabilities affecting popular software, "360 Safeguard(12.1.0.1004,12.1.0.1005,13.1.0.1001)" , "360 Total Security(10.8.0.1060,10.8.0.1213)", "360 Safe Browser & 360 Chrome(13.0.2170.0)". The attack vector is: On the browser vulnerability, just open a link to complete the vulnerability exploitation remotely; on the client software, you need to locally execute the vulnerability exploitation program, which of course can be achieved with the full chain of browser vulnerability. ΒΆΒΆ This is a set of the most serious vulnerabilities that exist on Qihoo 360's PC client a variety of popular software, remote vulnerabilities can be completed by opening a link to arbitrary code execution on both security browsers, with the use of local vulnerabilities, not only help the vulnerability code constitutes an escalation of privileges, er can make the spyware persistent without being scanned permanently resides on the target PC computer (because local vulnerability against Qihoo 360 company's antivirus kernel flaws); this group of remote and local vulnerability of the perfect match, to achieve an information security fallacy, in Qihoo 360's antivirus vulnerability, not only can not be scanned out of the virus, but will help the virus persistently control the target computer, while Qihoo 360 claims to be a safe browser, which exists in the kernel vulnerability but helped the composition of the remote vulnerability. (Security expert "Memory Corruptor" have reported this set of vulnerabilities to the corresponding vendor, all vulnerabilities have been fixed and the vendor rewarded thousands of dollars to the security experts) Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2021-33971? It affects 1 product. Products: 360 Total Security. ## How do I fix CVE-2021-33971? No fix has been published for CVE-2021-33971 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-33971 being exploited? There is no known exploitation of CVE-2021-33971 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2021-33974](https://insights.sbomify.com/CVE-2021-33974/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-33971 and fix it if it is affected. What it is: CVE-2021-33971 is a high-severity memory corruption vulnerability in n/a, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-33971 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-33971/ (Markdown: https://insights.sbomify.com/CVE-2021-33971/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-33971 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-33971 - OSV: https://osv.dev/vulnerability/CVE-2021-33971 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-33971/ Summaries are generated and may contain mistakes; the official description above is the record.