# CVE-2020-9753: Security feature bypass in Whale Browser Installer

> The Whale Browser Installer fails to verify signatures for the Flash installer, allowing attackers to execute arbitrary code via malicious installers.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6c4x-xqjq-96hr

## What is CVE-2020-9753?

CVE-2020-9753 is a critical vulnerability in NAVER Corporation Whale Browser Installer, published on 20 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Whale Browser Installer before 1.2.0.5 versions don't support signature verification for Flash installer.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2020-9753?

It affects 1 product.


Products: Naver Whale Browser Installer.

## How do I fix CVE-2020-9753?

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

## Is CVE-2020-9753 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9753 and fix it if it is affected.

What it is: CVE-2020-9753 is a critical vulnerability in NAVER Corporation Whale Browser Installer, published on 20 May 2020. 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-2020-9753 in the wild and no public exploit code.

Affected product: NAVER Corporation Whale Browser Installer. 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-2020-9753/ (Markdown: https://insights.sbomify.com/CVE-2020-9753/index.md)
```

## Sources

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

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