CVE-2014-0128
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 · uneditedSquid 3.1 before 3.3.12 and 3.4 before 3.4.4, when SSL-Bump is enabled, allows remote attackers to cause a denial of service (assertion failure) via a crafted range request, related to state management.
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 confidenceSquid proxy server versions 3.1 before 3.3.12 and 3.4 before 3.4.4 contain a vulnerability when SSL-Bump (HTTPS interception) is enabled. A remote attacker can send a crafted HTTP range request that triggers an assertion failure due to improper state management, causing the proxy to crash and result in denial of service.
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= 3.1= 3.1.0.1= 3.1.0.2= 3.1.0.3= 3.1.0.4= 3.1.0.5= 3.1.0.6= 3.1.0.7= 3.1.0.8= 3.1.0.9= 3.1.0.10= 3.1.0.11= 11.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Squid is installedRun 'squid -v' or check for the squid process with 'ps aux | grep squid'Affected if Squid is not installed on the system
-
Determine installed Squid versionRun 'squid -v' and note the version number in the output (e.g., 3.1.23, 3.4.2)Affected if Version is 3.1.x lower than 3.3.12, or 3.4.x lower than 3.4.4
-
Check if SSL-Bump is enabledInspect the Squid configuration file (typically /etc/squid/squid.conf) and search for 'ssl_bump' directiveAffected if SSL-Bump directive is present and configured (vulnerability only applies when SSL-Bump is enabled)
-
Confirm HTTPS interception is in useLook for related SSL-Bump directives such as 'sslproxy_cert_error' or 'sslproxy_flags' in squid.conf, or check if Squid is binding to port 443Affected if HTTPS interception features are actively configured
User is affected if Squid version is 3.1.x before 3.3.12 or 3.4.x before 3.4.4 AND SSL-Bump (HTTPS interception) is enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Squid to version 3.3.12 or later for the 3.1 branch, or 3.4.4 or later for the 3.4 branch. If immediate upgrade is not feasible, consider disabling SSL-Bump if HTTPS interception is not critically required, though this significantly impacts the proxy's functionality.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0128 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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