# CVE-2003-0080: Missing authorization in n/a

> Attackers can bypass firewall restrictions if packet forwarding is enabled due to missing iptables FORWARD chain rules in Gnome-lokkit.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2frv-wg69-9638

## What is CVE-2003-0080?

CVE-2003-0080 is a high-severity missing authorization vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The iptables ruleset in Gnome-lokkit in Red Hat Linux 8.0 does not include any rules in the FORWARD chain, which could allow attackers to bypass intended access restrictions if packet forwarding is enabled.

## Which versions are affected by CVE-2003-0080?

It affects 1 product.


Products: Gnome Gnome-Lokkit.

## How do I fix CVE-2003-0080?

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

## Is CVE-2003-0080 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0080 and fix it if it is affected.

What it is: CVE-2003-0080 is a high-severity missing authorization vulnerability in n/a, published on 18 Mar 2003. 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-2003-0080 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-2003-0080/ (Markdown: https://insights.sbomify.com/CVE-2003-0080/index.md)
```

## Sources

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

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