Homepage
About Snyk

Access Restriction Bypass Affecting libspring-java package, versions <4.3.2-1

Severity

 Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment

    Threat Intelligence

    EPSS
    0.23% (62nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-DEBIANUNSTABLE-LIBSPRINGJAVA-384949
  • published 25 May 2017
  • disclosed 25 May 2017
Report a new vulnerability Found a mistake?

Introduced: 25 May 2017

CVE-2016-5007 Open this link in a new tab
CWE-264 Open this link in a new tab

How to fix?

Upgrade Debian:unstable libspring-java to version 4.3.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libspring-java package and not the libspring-java package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Both Spring Security 3.2.x, 4.0.x, 4.1.0 and the Spring Framework 3.2.x, 4.0.x, 4.1.x, 4.2.x rely on URL pattern mappings for authorization and for mapping requests to controllers respectively. Differences in the strictness of the pattern matching mechanisms, for example with regards to space trimming in path segments, can lead Spring Security to not recognize certain paths as not protected that are in fact mapped to Spring MVC controllers that should be protected. The problem is compounded by the fact that the Spring Framework provides richer features with regards to pattern matching as well as by the fact that pattern matching in each Spring Security and the Spring Framework can easily be customized creating additional differences.