dbcve.org
SquidApplication

CVE-2007-0247

MEDIUM · 5.0 CVSS v2.0 Published 2007-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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/src/ftp.c in Squid before 2.6.STABLE7 allows remote FTP servers to cause a denial of service (core dump) via crafted FTP directory listing responses, possibly related to the (1) ftpListingFinish and (2) ftpHtmlifyListEntry functions.

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 · high confidence

Squid proxy server before version 2.6.STABLE7 contains a vulnerability in the FTP directory listing parser (squid/src/ftp.c). When processing responses from FTP servers, the ftpListingFinish and ftpHtmlifyListEntry functions can be triggered by specially crafted FTP directory listings to cause a core dump, resulting in a denial of service. This is exploitable remotely by malicious or compromised FTP servers that the Squid proxy communicates with.

MitigationUpgrade Squid to version 2.6.STABLE7 or later to obtain the fix for this vulnerability. As a defensive measure, consider restricting FTP proxy access to trusted internal FTP servers only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.6.stable1= 2.6.stable2= 2.6.stable3= 2.6.stable4= 2.6.stable5= 2.6.stable6

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
None
Integrity
None
Availability
Partial

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Squid version
    Run 'squid -v' or 'squid -V' to display version information
    Affected if Version displayed is 2.6.stable1, 2.6.stable2, 2.6.stable3, 2.6.stable4, 2.6.stable5, or 2.6.stable6
  2. Check if FTP proxy service is enabled
    Inspect Squid configuration file (typically squid.conf) for ftp_access rules or FTP port configurations (usually port 21)
    Affected if FTP proxy access rules exist and Squid is configured to handle FTP requests
  3. Verify Squid is configured to proxy FTP connections
    Look for 'ftp' in acl types or http_access rules that permit FTP traffic
    Affected if Configuration allows FTP proxy requests to external servers
  4. Identify FTP server access scope
    Review ACLs controlling which FTP servers Squid can connect to (such as src or dst ACLs restricting FTP destinations)
    Affected if Squid can connect to untrusted or external FTP servers without restriction

You are affected if Squid version is between 2.6.stable1 and 2.6.stable6 inclusive AND FTP proxy functionality is enabled, allowing Squid to process FTP directory listings from servers it connects to.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Squid to version 2.6.STABLE7 or later to obtain the fix for this vulnerability. As a defensive measure, consider restricting FTP proxy access to trusted internal FTP servers only.

Fix this in Squid Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0247 — 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-2007-0247 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