# CVE-2021-33592: Code injection in NAVER Toolbar

> Remote attackers can execute arbitrary code by exploiting a code signing bypass in the NAVER Toolbar upgrade mechanism.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v67h-j6jf-6wcf

## What is CVE-2021-33592?

CVE-2021-33592 is a critical code injection vulnerability in NAVER Toolbar, published on 19 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NAVER Toolbar before 4.0.30.323 allows remote attackers to execute arbitrary code via a crafted upgrade.xml file. Special characters in filename parameter can be the cause of bypassing code signing check function.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2021-33592?

It affects 1 product.


Products: Naver Toolbar.

## How do I fix CVE-2021-33592?

No fix has been published for CVE-2021-33592 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-33592 being exploited?

There is no known exploitation of CVE-2021-33592 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-33592 and fix it if it is affected.

What it is: CVE-2021-33592 is a critical code injection vulnerability in NAVER Toolbar, published on 19 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-33592 in the wild and no public exploit code.

Affected product: NAVER Toolbar. 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-33592/ (Markdown: https://insights.sbomify.com/CVE-2021-33592/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-33592
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-33592
- OSV: https://osv.dev/vulnerability/CVE-2021-33592

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-33592/
Summaries are generated and may contain mistakes; the official description above is the record.