CVE-2005-2317: 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

This month

HIGH 7.5DOWNGRADE

CVE-2005-2317 is a high-severity flaw (CVSS 7.5) affecting shorewall. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Published	2005-07-19
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: shorewall

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-07-19 04:00 UTCPublished CVE record published
2026-06-16 22:14 UTCUpdated Record last modified

shorewall shorewall DOWNGRADE

Affected: 2.0.0 · 2.0.0a · 2.0.0b · 2.0.1 · 2.0.2 · 2.0.2a · 2.0.2b · 2.0.2c

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy shorewall || rpm -q shorewall || shorewall --version

2. No fixed release: DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison shorewall sudo apt install shorewall=<VERSION_BEFORE_2.0.0> sudo apt-mark hold shorewall

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list shorewall sudo dnf downgrade shorewall-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add shorewall

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-2317?

shorewall: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2317 being exploited?

CVE-2005-2317 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-2317 affect?

CVE-2005-2317 affects shorewall. Severity is high (CVSS 7.5). 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 po

How urgent is CVE-2005-2317?

Priority 47/100. High severity

Related CVEs

CVE-2004-0647 MEDIUM 4.6 DOWNGRADE shorewall 1.4.10c and earlier, and 2.0.x before 2.0.3a, allows local users to overwrite arbitrary files via a

References

← Back to latest CVEs