Debian LinuxOperating system · Debian
CVE-2016-10711
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 · uneditedApsis Pound before 2.8a allows request smuggling via crafted headers, a different vulnerability than CVE-2005-3751.
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 · moderate confidenceA request smuggling vulnerability in Apsis Pound (reverse proxy/load balancer) before version 2.8a allows attackers to craft malicious HTTP headers to bypass security controls, poison web caches, or intercept/alter traffic between clients and backend servers.
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
Debian LinuxOperating system
= 7.0<= 2.7CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Apsis Pound is installedRun 'which pound' or on Debian check 'dpkg -l | grep pound'Affected if Apsis Pound package is present on the system
-
Determine installed Pound versionRun 'pound -V' or 'pound -v' to display version information, or on Debian use 'dpkg -l pound'Affected if The displayed version is 2.7 or lower, or on Debian 7.0 the version is unpatched
-
Confirm Pound is actively runningRun 'ps aux | grep pound' or 'systemctl status pound' (or 'service pound status')Affected if Pound process is running as a daemon
-
Inspect Pound configuration for proxy usageExamine the Pound configuration file typically at /etc/pound/pound.cfg and look for 'ListenHTTP' or 'Backend' directives that define reverse proxy behaviorAffected if Configuration contains active ListenHTTP sections and Backend definitions that route traffic to upstream servers
You are affected if Apsis Pound version 2.7 or lower is installed AND actively running as a reverse proxy with frontend/backend configurations.
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.
dbcve · scopedUpgrade Apsis Pound to version 2.8a or later. If immediate upgrade is not feasible, implement strict input validation on upstream servers and monitor for anomalous request patterns.
Pound 2.8a or later
- 1. Check the current installed version of Pound: `dpkg -l | grep pound` or `pound -V`
- 2. For Debian systems: Update package lists with `apt-get update`
- 3. Upgrade Pound to version 2.8a or later: `apt-get install pound` or `apt-get install pound=2.8a`
- 4. Verify the installed version matches the fixed release: `dpkg -l | grep pound`
- 5. Restart the Pound service to apply changes: `service pound restart` or `systemctl restart pound`
- 6. Test that the service is running and headers are processed correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10711 — 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-2016-10711 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