dbcve.org
SquidApplication

CVE-2005-0194

HIGH · 10.0 CVSS v2.0 Published 2005-05-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Squid 2.5, when processing the configuration file, parses empty Access Control Lists (ACLs), including proxy_auth ACLs without defined auth schemes, in a way that effectively removes arguments, which could allow remote attackers to bypass intended ACLs if the administrator ignores the parser warnings.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SquidApplication
Affected:= 2.0.patch1= 2.0.patch2= 2.0.pre1= 2.0.release= 2.1.patch1= 2.1.patch2= 2.1.pre1= 2.1.pre3= 2.1.pre4= 2.1.release= 2.2.devel3= 2.2.devel4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch distro.conectiva.com.br →
Recommended fix Moderate confidence

Squid 2.5.STABLE7 or later (preferably latest 2.5.STABLE series or 3.x)

  1. 1. Identify all Squid proxy servers running versions 2.0.patch1, 2.0.patch2, 2.0.pre1, or 2.0.release in your environment
  2. 2. Back up the current Squid configuration file (squid.conf) and any related ACL definitions
  3. 3. Stop the Squid service before performing the upgrade
  4. 4. Upgrade Squid to version 2.5.STABLE7 or later (2.5.STABLE10+ recommended for additional security fixes)
  5. 5. Restore or migrate the backed-up squid.conf configuration
  6. 6. Review configuration for any empty ACL definitions or proxy_auth ACLs without defined auth schemes and correct them
  7. 7. Start the Squid service and verify access controls are functioning correctly
  8. 8. Test that the ACLs are properly enforcing the intended access restrictions
Caveat Squid 2.5 introduced changes to configuration syntax and authentication helpers; some directives may require updates from 2.0 configuration files

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-0194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-0194 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data