# CVE-2005-2317: Security feature bypass in n/a

> Remote attackers with accepted MAC addresses can bypass firewall rules in Shorewall when specific MAC list configurations are enabled.

- **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:** Yes
- **Published:** 19 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2317, DSA-849-1, GHSA-jq9c-9fj7-fg5g

## What is CVE-2005-2317?

CVE-2005-2317 is a high-severity vulnerability in n/a, published on 19 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shorewall 2.4.x before 2.4.1, 2.2.x before 2.2.5, and 2.0.x before 2.0.17, when MACLIST_TTL is greater than 0 or MACLIST_DISPOSITION is set to ACCEPT, allows remote attackers with an accepted MAC address to bypass other firewall rules or policies.

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

It affects 1 product.


Products: Shorewall Shorewall.

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

Upgrade to a fixed version.

## Is CVE-2005-2317 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0647](https://insights.sbomify.com/CVE-2004-0647/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2317 is a high-severity vulnerability in n/a, published on 19 Jul 2005. 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-2005-2317 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-2317/ (Markdown: https://insights.sbomify.com/CVE-2005-2317/index.md)
```

## Sources

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

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