CoreCVE
Back

MEDIUM

spring-framework: Improper URL path validation allows for bypassing of security checks on static resources

Published Mar 16, 2018

Description

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 security constraints. By adding a URL path parameter with special encodings, 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. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.

Affected products

Remediation

Red Hat mitigation

As a general precaution, users are encouraged to separate public and private resources. For example, separating static resources and mapping them to /resources/public/** and /resources/private/** is preferred to having one common root with mixed public and private resource content underneath.

Metrics

Weaknesses (1)

CWE-20

Improper Input Validation

References (20)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner dell
Published Mar 16, 2018
Updated Sep 16, 2024
Reserved Dec 6, 2017
Link CVE-2018-1199
CISA Vulnrichment
Updated n/a
NVD
Status Modified
Modified Jun 17, 2026
Link CVE-2018-1199
Red Hat
Severity Important
Public date Jan 29, 2018
Links CVE-2018-1199 - Bugzilla
GHSA-V596-FWHQ-8X48