# CVE-2001-0969: Security feature bypass in n/a

> Attackers can bypass ipfw firewall rules on FreeBSD point-to-point interfaces, allowing unauthorized remote connections.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-w3rj-c78v-v7qr

## What is CVE-2001-0969?

CVE-2001-0969 is a critical vulnerability in Freebsd Freebsd, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ipfw in FreeBSD does not properly handle the use of "me" in its rules when point to point interfaces are used, which causes ipfw to allow connections from arbitrary remote hosts.

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2001-0969 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0969 is a critical vulnerability in Freebsd Freebsd, published on 9 Mar 2002. 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-2001-0969 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-0969/ (Markdown: https://insights.sbomify.com/CVE-2001-0969/index.md)
```

## Sources

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

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