CVE-2005-1711: Gibraltar Firewall 2.2 and earlier, when using the ClamAV update to 0.81 for Squid, uses a defunct ClamAV meth

This month

HIGH 7.5DOWNGRADEDOWNGRADEDOWNGRADE

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

Gibraltar Firewall 2.2 and earlier, when using the ClamAV update to 0.81 for Squid, uses a defunct ClamAV method to scan memory for viruses, which does not return an error code and prevents viruses from being detected.

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	1.0% (top 36%)
CISA exploited list	No
Published	2005-05-24
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: clam anti-virus · gibraltar · squid

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

Am I affected?

Timeline

2005-05-24 04:00 UTCPublished CVE record published
2026-06-16 22:13 UTCUpdated Record last modified

clam anti-virus clamav DOWNGRADE

Affected: 0.90.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.90.2

1. Check installed version

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

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

apt-cache madison clamav sudo apt install clamav=<VERSION_BEFORE_0.90.2> sudo apt-mark hold clamav

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

dnf --showduplicates list clamav sudo dnf downgrade clamav-<VERSION_BEFORE_0.90.2> sudo dnf versionlock add clamav

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.

gibraltar gibraltar firewall DOWNGRADE

Affected: 2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2

1. Check installed version

apt-cache policy gibraltar-firewall || rpm -q gibraltar-firewall || gibraltar-firewall --version

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

apt-cache madison gibraltar-firewall sudo apt install gibraltar-firewall=<VERSION_BEFORE_2.2> sudo apt-mark hold gibraltar-firewall

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

dnf --showduplicates list gibraltar-firewall sudo dnf downgrade gibraltar-firewall-<VERSION_BEFORE_2.2> sudo dnf versionlock add gibraltar-firewall

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.

squid squid DOWNGRADE

Affected: 2.6.stable1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.6.stable1

1. Check installed version

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

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

apt-cache madison squid sudo apt install squid=<VERSION_BEFORE_2.6.stable1> sudo apt-mark hold squid

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

dnf --showduplicates list squid sudo dnf downgrade squid-<VERSION_BEFORE_2.6.stable1> sudo dnf versionlock add squid

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-1711?

clamav: downgrade or apply the listed mitigation; gibraltar firewall: downgrade or apply the listed mitigation; squid: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1711 being exploited?

CVE-2005-1711 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-1711 affect?

CVE-2005-1711 affects clamav, gibraltar firewall, squid. Severity is high (CVSS 7.5). Gibraltar Firewall 2.2 and earlier, when using the ClamAV update to 0.81 for Squid, uses a defunct ClamAV method to scan memory for viruses, which does not return an error code and prevents viruses from being detected.

How urgent is CVE-2005-1711?

Priority 42/100. High severity

Software pages

Squid vulnerabilities

Related CVEs

CVE-2026-20213 HIGH 7.5 UPGRADE UPGRADE A vulnerability in the PE file format parser of ClamAV could allow an unauthenticated, remote attacker to caus
CVE-2026-20214 HIGH 7.5 UPGRADE UPGRADE A vulnerability in the FSG file format parser of ClamAV could allow an unauthenticated, remote attacker to cau
CVE-2026-20215 HIGH 7.5 UPGRADE UPGRADE A vulnerability in the 7z file format parser of ClamAV could allow an unauthenticated, remote attacker to caus
CVE-2026-20216 HIGH 7.5 UPGRADE UPGRADE A vulnerability in the InstallShield file format parser of ClamAV could allow an unauthenticated, remote attac
CVE-2026-20217 HIGH 7.5 UPGRADE UPGRADE A vulnerability in the PESpin file format parser of ClamAV could allow an unauthenticated, remote attacker to

References

← Back to latest CVEs