high
7.5
CWE
417
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2016-9879

First published: Tue Jan 03 2017(Updated: )

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.

Credit: security_alert@emc.com security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
redhat/springframework-security<3.2.10
3.2.10
redhat/springframework-security<4.1.4
4.1.4
redhat/springframework-security<4.2.1
4.2.1
maven/org.springframework.security:spring-security-core>=4.2.0.RELEASE<4.2.1.RELEASE
4.2.1.RELEASE
maven/org.springframework.security:spring-security-core>=4.0.0.RELEASE<4.1.4.RELEASE
4.1.4.RELEASE
maven/org.springframework.security:spring-security-core<3.2.10.RELEASE
3.2.10.RELEASE
Spring Security=3.2.0
Spring Security=3.2.1
Spring Security=3.2.2
Spring Security=3.2.3
Spring Security=3.2.4
Spring Security=3.2.5
Spring Security=3.2.6
Spring Security=3.2.7
Spring Security=3.2.8
Spring Security=3.2.9
Spring Security=4.1.0
Spring Security=4.1.1
Spring Security=4.1.2
Spring Security=4.1.3
Spring Security=4.2.0
IBM WebSphere Application Server=8.5.0.0
IBM WebSphere Application Server=8.5.0.1
IBM WebSphere Application Server=8.5.0.2
IBM WebSphere Application Server=8.5.5.0
IBM WebSphere Application Server=8.5.5.1
IBM WebSphere Application Server=8.5.5.2
IBM WebSphere Application Server=8.5.5.3
IBM WebSphere Application Server=8.5.5.4
IBM WebSphere Application Server=8.5.5.5
IBM WebSphere Application Server=8.5.5.6
IBM WebSphere Application Server=8.5.5.7
IBM WebSphere Application Server=8.5.5.8
IBM WebSphere Application Server=8.5.5.9

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-9879?

    CVE-2016-9879 has a high severity rating due to its potential to allow unauthorized access.

  • How do I fix CVE-2016-9879?

    To fix CVE-2016-9879, upgrade to Spring Security version 3.2.10 or later, 4.1.4 or later, or 4.2.1 or later.

  • Which versions of Spring Security are affected by CVE-2016-9879?

    CVE-2016-9879 affects Spring Security versions prior to 3.2.10, 4.1.4, and 4.2.1.

  • What type of vulnerability is CVE-2016-9879?

    CVE-2016-9879 is a security vulnerability that allows attackers to bypass security constraints via URL path parameters.

  • Is there a workaround for CVE-2016-9879 if I cannot upgrade?

    There is no specific documented workaround for CVE-2016-9879, so upgrading is recommended.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203