# CVE-2020-9264: Security feature bypass in n/a

> Attackers can bypass virus detection in ESET products by crafting specific ZIP archive fields, allowing malicious files to evade scanning.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8phc-x6hp-m8fj

## What is CVE-2020-9264?

CVE-2020-9264 is a medium-severity vulnerability in n/a, published on 18 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ESET Archive Support Module before 1296 allows virus-detection bypass via a crafted Compression Information Field in a ZIP archive. This affects versions before 1294 of Smart Security Premium, Internet Security, NOD32 Antivirus, Cyber Security Pro (macOS), Cyber Security (macOS), Mobile Security for Android, Smart TV Security, and NOD32 Antivirus 4 for Linux Desktop.

Weakness: CWE-436 (Interpretation Conflict)

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

It affects 6 products.


Products: Eset Cyber Security, Eset Internet Security, Eset Mobile Security, Eset Nod32 Antivirus, Eset Smart Security, Eset Smart Tv Security.

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

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

## Is CVE-2020-9264 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10180](https://insights.sbomify.com/CVE-2020-10180/): Security feature bypass in n/a (critical 9.8)
- [CVE-2023-2847](https://insights.sbomify.com/CVE-2023-2847/): Local privilege escalation in ESET products for Linux and MacOS (high 7.8)
- [CVE-2019-16519](https://insights.sbomify.com/CVE-2019-16519/): Privilege escalation in n/a (high 7.8)
- [CVE-2020-10193](https://insights.sbomify.com/CVE-2020-10193/): Security feature bypass in n/a (high 7.5)
- [CVE-2019-17549](https://insights.sbomify.com/CVE-2019-17549/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9264 is a medium-severity vulnerability in n/a, published on 18 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-9264 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-2020-9264/ (Markdown: https://insights.sbomify.com/CVE-2020-9264/index.md)
```

## Sources

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

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