Spring Framework Vulnerability: CVE-2016-5007 in libspring-java Packages

libspring-java Updated 03 Oct 2025

Summary

25/05/2017
N/A
No i
High
7.5

UBUNTU-CVE-2016-5007: 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. Affects libspring-java versions 3.0.6.RELEASE-10 – 3.0.6.RELEASE-9. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The libspring-java package is a collection of libraries that provide comprehensive support for building Java applications. It includes core functionalities such as dependency injection, aspect-oriented programming, and transaction management. This package is widely used in enterprise applications due to its flexibility and powerful features. However, it has been identified to have a vulnerability that affects its security mechanisms, particularly in how it handles URL pattern mappings for authorization.

Vulnerability Detail

CVE-2016-5007 is a vulnerability in the Spring Framework that affects versions 3.2.x, 4.0.x, 4.1.x, and 4.2.x. The issue arises from differences in the strictness of URL pattern matching mechanisms, which can lead to Spring Security failing to recognize certain paths as protected. This could allow unauthorized access to resources that should be secured, potentially exposing sensitive data or functionality. The vulnerability is compounded by the ability to customize pattern matching, which can create further discrepancies in security enforcement.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can implement stricter URL pattern matching in your Spring Security configuration to ensure that all paths are correctly recognized as protected. This may involve reviewing and adjusting your security configuration to avoid relying solely on default pattern matching.

Conclusion

CVE-2016-5007 is a significant vulnerability in the Spring Framework that can lead to unauthorized access due to improper URL pattern matching. It is crucial for users of the libspring-java package to update to the patched versions to ensure the security of their applications. Implementing stricter URL matching as a workaround can also help mitigate risks until the update is applied.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2016-5007 is a vulnerability in the Spring Framework that affects how URL patterns are matched for authorization, potentially allowing unauthorized access to protected resources.

The affected versions include libspring-java 3.0.6.RELEASE-13ubuntu0.1~esm2 and 3.2.13-5ubuntu0.1~esm1, among others.

You can use the Vulert platform to check if your application is affected by this vulnerability by simply uploading your manifest file like package-lock.json.

The vulnerability could lead to unauthorized access to sensitive data or functionality in your application, which may result in data breaches or other security incidents.

Yes, a patched version of the libspring-java package is available. It is recommended to update to the latest version to mitigate the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback