CVE-2015-1380
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 · uneditedjcc.c in Privoxy before 3.0.23 allows remote attackers to cause a denial of service (abort) via a crafted chunk-encoded body.
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 confidenceA denial of service vulnerability exists in Privoxy's jcc.c component (handling chunked HTTP encoding) prior to version 3.0.23. Remote attackers can trigger an abort condition by sending a specially crafted chunk-encoded HTTP body to the proxy server.
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.0.22= 11.2= 13.1= 13.2CVSS 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.
-
Check if Privoxy is installedOn Linux/Unix: run 'which privoxy' or check package manager (dpkg -l | grep privoxy, rpm -qa | grep privoxy). On Solaris: pkginfo | grep -i privoxy.Affected if Privoxy is not found on the system (not affected).
-
Determine installed Privoxy versionRun 'privoxy --version' or 'privoxy -v'. For package-based systems: 'dpkg -l privoxy' or 'rpm -q privoxy'.Affected if Version is 3.0.22 or lower, or version cannot be determined (likely affected).
-
Verify Privoxy service is running and exposedCheck process status: 'ps aux | grep privoxy' or 'systemctl status privoxy'. Check listening ports: 'netstat -tlnp | grep 8118' (default Privoxy port).Affected if Service is running and listening on a network port (vulnerable if version <= 3.0.22).
-
Confirm chunked encoding handling is activePrivoxy operates as an HTTP proxy by default. Check config file (usually /etc/privoxy/config or /usr/local/etc/privoxy/config) for 'listen-address' directive to confirm it accepts HTTP connections.Affected if Privoxy is configured to handle HTTP proxy requests (standard configuration) - the vulnerable code path is active.
System is affected if Privoxy is installed with version 3.0.22 or lower and the service is running as an HTTP proxy (listening on a network interface for chunked HTTP encoding requests).
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 Privoxy to version 3.0.23 or later to receive the patch for this vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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 $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1380 — 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-2015-1380 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