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

> Local attackers can bypass Tiny Personal Firewall filtering by sending non-standard TCP packets via non-Windows protocol adapters.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xgj9-vjq9-qmrc

## What is CVE-2001-1549?

CVE-2001-1549 is a low-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tiny Personal Firewall 1.0 and 2.0 allows local users to bypass filtering via non-standard TCP packets created with non-Windows protocol adapters.

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

It affects 1 product.


Products: Tiny Software Tiny Personal Firewall.

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

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

## Is CVE-2001-1549 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1549 exists.

Public exploit code:

- ZoneAlarm Pro 1.0/2.x - Outbound Packet Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2002-1925](https://insights.sbomify.com/CVE-2002-1925/): Denial of service in n/a (medium 5.0)
- [CVE-2002-0349](https://insights.sbomify.com/CVE-2002-0349/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1549 is a low-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1549 exists.

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

## Sources

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

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