Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:maven/org.springframework/spring-core@5.0.2.RELEASE
purl pkg:maven/org.springframework/spring-core@5.0.2.RELEASE
Next non-vulnerable version 5.0.3
Latest non-vulnerable version 6.2.11
Risk 3.4
Vulnerabilities affecting this package (5)
Vulnerability Summary Fixed by
VCID-2327-21sr-mfgx
Aliases:
CVE-2018-1272
GHSA-4487-x383-qpph
Improper Privilege Management When Spring MVC or Spring WebFlux server application (server A) receives input from a remote client, and then uses that input to make a multipart request to another server (server B), it can be exposed to an attack, where an extra multipart is inserted in the content of the request from server A, causing server B to use the wrong value for a part it expects. This could to lead privilege escalation, for example, if the part content represents a username or user roles.
5.0.5
Affected by 0 other vulnerabilities.
5.0.5.RELEASE
Affected by 3 other vulnerabilities.
VCID-3p1k-4ges-1fev
Aliases:
CVE-2019-3795
GHSA-v2r2-7qm7-jj6v
Insufficient Entropy in PRNG Spring Security contain an insecure randomness vulnerability when using `SecureRandomFactoryBean#setSeed` to configure a `SecureRandom` instance. In order to be impacted, an honest application must provide a seed and make the resulting random material available to an attacker for inspection.
5.0.12.RELEASE
Affected by 1 other vulnerability.
5.0.13.RELEASE
Affected by 1 other vulnerability.
5.1.5.RELEASE
Affected by 1 other vulnerability.
5.1.6.RELEASE
Affected by 1 other vulnerability.
VCID-72ga-q9u7-sfav
Aliases:
CVE-2018-1275
GHSA-3rmv-2pg5-xvqj
Improperly Implemented Security Check for Standard Spring Framework allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.
5.0.5
Affected by 0 other vulnerabilities.
5.0.5.RELEASE
Affected by 3 other vulnerabilities.
VCID-fra1-reqm-kfdb
Aliases:
CVE-2020-5421
GHSA-rv39-3qh7-9v7w
Remote file disclosure In Spring Framework the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
5.0.18.RELEASE
Affected by 0 other vulnerabilities.
5.0.19.RELEASE
Affected by 0 other vulnerabilities.
5.1.17.RELEASE
Affected by 0 other vulnerabilities.
5.1.18.RELEASE
Affected by 0 other vulnerabilities.
5.2.8.RELEASE
Affected by 0 other vulnerabilities.
5.2.9.RELEASE
Affected by 0 other vulnerabilities.
VCID-h4kj-zdr8-wbdr
Aliases:
CVE-2018-1199
GHSA-v596-fwhq-8x48
Improper Input Validation Spring Security 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.
5.0.3
Affected by 0 other vulnerabilities.
5.0.3.RELEASE
Affected by 4 other vulnerabilities.
Vulnerabilities fixed by this package (1)
Vulnerability Summary Aliases
VCID-h4kj-zdr8-wbdr Improper Input Validation Spring Security 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. CVE-2018-1199
GHSA-v596-fwhq-8x48