Spring Framework Vulnerability: Bypass of Security Constraints in libspring-java

libspring-java Updated 03 Oct 2025

Summary

16/03/2018
N/A
No i
Medium
5.3

UBUNTU-CVE-2018-1199: Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing secu... 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libspring-java is a core component of the Spring Framework, which is widely used for building enterprise-level Java applications. It provides comprehensive infrastructure support for developing Java applications, including features for dependency injection, aspect-oriented programming, and transaction management. However, certain versions of this package are vulnerable to a security issue that allows attackers to bypass security constraints through manipulated URL path parameters.

Vulnerability Detail

The vulnerability, identified as CVE-2018-1199, arises from Spring Security's failure to properly handle URL path parameters when processing security constraints. This issue affects multiple versions of Spring Security and the Spring Framework, allowing attackers to exploit the ambiguity in how different servlet containers handle path parameters. By using special encodings in URL path parameters, an attacker can potentially bypass security measures, leading to unauthorized access to secured resources. The root cause is a lack of clarity in the Servlet Specification regarding path parameter handling, which can result in serious security breaches.

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, consider implementing additional input validation or sanitization on URL parameters to mitigate the risk of bypassing security constraints until the package can be updated.

Conclusion

The CVE-2018-1199 vulnerability in libspring-java poses a significant risk by allowing attackers to bypass security constraints through manipulated URL path parameters. It is crucial for users to update to the latest patched versions of the package to mitigate this risk. Additionally, temporary workarounds can be implemented to enhance security until updates are applied.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2018-1199 is a vulnerability in the Spring Framework that allows attackers to bypass security constraints by manipulating URL path parameters.

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 playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of CVE-2018-1199 is 5.3, indicating a medium severity level.

If immediate updates are not possible, consider implementing input validation or sanitization on URL parameters as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

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