# CVE-2001-0166: Denial of service in n/a

> Remote attackers can cause a denial of service in the Flash plugin by tricking users into opening malformed SWF files.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8768-4fq8-2xfv

## What is CVE-2001-0166?

CVE-2001-0166 is a high-severity denial of service vulnerability in n/a, published on 7 May 2001. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Macromedia Shockwave Flash plugin version 8 and earlier allows remote attackers to cause a denial of service via malformed tag length specifiers in a SWF file.

## Which versions are affected by CVE-2001-0166?

It affects 1 product.


Products: Macromedia Shockwave Flash Plugin.

## How do I fix CVE-2001-0166?

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

## Is CVE-2001-0166 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1525](https://insights.sbomify.com/CVE-1999-1525/): Information disclosure in n/a (medium 5.1)
- [CVE-1999-1526](https://insights.sbomify.com/CVE-1999-1526/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0166 and fix it if it is affected.

What it is: CVE-2001-0166 is a high-severity denial of service vulnerability in n/a, published on 7 May 2001. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2001-0166 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-2001-0166/ (Markdown: https://insights.sbomify.com/CVE-2001-0166/index.md)
```

## Sources

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

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