# CVE-2005-2533: Denial of service in n/a

> Authenticated remote attackers can cause memory exhaustion and denial of service in OpenVPN servers configured in dev tap mode by flooding spoofed MAC addresses.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2533, GHSA-q7pv-xr8p-6j5f

## What is CVE-2005-2533?

CVE-2005-2533 is a low-severity denial of service vulnerability in n/a, published on 24 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenVPN before 2.0.1, when running in "dev tap" Ethernet bridging mode, allows remote authenticated clients to cause a denial of service (memory exhaustion) via a flood of packets with a large number of spoofed MAC addresses.

## Which versions are affected by CVE-2005-2533?

It affects 1 product.


Products: Openvpn Openvpn.

## How do I fix CVE-2005-2533?

Upgrade to a fixed version.

## Is CVE-2005-2533 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-12106](https://insights.sbomify.com/CVE-2025-12106/): Memory corruption in OpenVPN (critical 9.1)
- [CVE-2024-5594](https://insights.sbomify.com/CVE-2024-5594/): Information disclosure in OpenVPN (critical 9.1)
- [CVE-2018-7544](https://insights.sbomify.com/CVE-2018-7544/): Cross-site request forgery in n/a (critical 9.1)
- [CVE-2006-1629](https://insights.sbomify.com/CVE-2006-1629/): Code injection in n/a (critical 9.0)
- [CVE-2024-4877](https://insights.sbomify.com/CVE-2024-4877/): Privilege escalation in OpenVPN (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2533 and fix it if it is affected.

What it is: CVE-2005-2533 is a low-severity denial of service vulnerability in n/a, published on 24 Aug 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-2533 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-2005-2533/ (Markdown: https://insights.sbomify.com/CVE-2005-2533/index.md)
```

## Sources

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

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