CVE-2016-9879
No exploitation reported by the sources we read.
- Published2017-01-06
- WeaknessCWE-417
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected.
Timeline
dates in UTC- 2017-01-0622:59CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-9879?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-9879?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.5 | = 8.5.0.0 | no fix published | NVD |
| 8.5 | = 8.5.0.1 | no fix published | NVD |
| 8.5 | = 8.5.0.2 | no fix published | NVD |
| 8.5 | = 8.5.5.0 | no fix published | NVD |
| 8.5 | = 8.5.5.1 | no fix published | NVD |
| 8.5 | = 8.5.5.2 | no fix published | NVD |
| 8.5 | = 8.5.5.3 | no fix published | NVD |
| 8.5 | = 8.5.5.4 | no fix published | NVD |
| 8.5 | = 8.5.5.5 | no fix published | NVD |
| 8.5 | = 8.5.5.6 | no fix published | NVD |
| 8.5 | = 8.5.5.7 | no fix published | NVD |
| 8.5 | = 8.5.5.8 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.2 | = 3.2.0 | no fix published | NVD |
| 3.2 | = 3.2.1 | no fix published | NVD |
| 3.2 | = 3.2.2 | no fix published | NVD |
| 3.2 | = 3.2.3 | no fix published | NVD |
| 3.2 | = 3.2.4 | no fix published | NVD |
| 3.2 | = 3.2.5 | no fix published | NVD |
| 3.2 | = 3.2.6 | no fix published | NVD |
| 3.2 | = 3.2.7 | no fix published | NVD |
| 3.2 | = 3.2.8 | no fix published | NVD |
| 3.2 | = 3.2.9 | no fix published | NVD |
| 4.1 | = 4.1.0 | no fix published | NVD |
| 4.1 | = 4.1.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.2 | ≥ 4.2.0.RELEASE, < 4.2.1.RELEASE | 4.2.1.RELEASE | OSV |
| 4.x | ≥ 4.0.0.RELEASE, < 4.1.4.RELEASE | 4.1.4.RELEASE | OSV |
| 3.2 | < 3.2.10.RELEASE | 3.2.10.RELEASE | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- pivotal.ioVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-417read 2026-10-23
- FIRST EPSSEPSS score1.5 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2017-01-06
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-9879?
Is CVE-2016-9879 actively exploited?
What is the CVSS score for CVE-2016-9879?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.