spring-security-web-4.0.2.RELEASE.jar: 11 vulnerabilities (highest severity is: 9.3) [vp-rem] (reachable)

<details>
  <summary>📂 Vulnerable Library - <strong>spring-security-web-4.0.2.RELEASE.jar</strong></summary>

spring-security-web



**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar


</details>


# Findings
| Finding | Severity | 🎯 CVSS | Exploit Maturity | EPSS | Library | Type | Fixed in | Remediation Available | **Reachability** |
| ------------- | ------------- | ---- | --- | ----- | ----- | ----- | --- | --- | --- |
| [ CVE-2022-22978 ](https://www.mend.io/vulnerability-database/CVE-2022-22978) | 🟣 Critical | 9.3 | Not Defined | 90.8% | spring-security-core-4.0.2.RELEASE.jar | Transitive | N/A | ❌ | |
| [ CVE-2022-22978 ](https://www.mend.io/vulnerability-database/CVE-2022-22978) | 🟣 Critical | 9.3 | Not Defined | 90.8% | spring-security-web-4.0.2.RELEASE.jar | Direct | org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-core:5.6.4,org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.6.4,https://github.com/spring-projects/spring-security.git - no_fix | ✅ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ CVE-2016-5007 ](https://www.mend.io/vulnerability-database/CVE-2016-5007) | 🔴 High | 8.7 | Not Defined | < 1% | spring-security-web-4.0.2.RELEASE.jar | Direct | org.springframework:spring-webmvc:4.3.0.RELEASE,org.springframework.security:spring-security-web:4.1.1.RELEASE,org.springframework.security:spring-security-config:4.1.1.RELEASE | ✅ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ CVE-2020-5407 ](https://www.mend.io/vulnerability-database/CVE-2020-5407) | 🔴 High | 8.7 | Not Defined | < 1% | spring-security-core-4.0.2.RELEASE.jar | Transitive | N/A | ❌ | |
| [ CVE-2021-22112 ](https://www.mend.io/vulnerability-database/CVE-2021-22112) | 🔴 High | 8.7 | Not Defined | 1.0% | spring-security-web-4.0.2.RELEASE.jar | Direct | org.springframework.security:spring-security-bom:5.4.4,org.springframework.security:spring-security-web:5.4.4,https://github.com/spring-projects/spring-security.git - no_fix | ✅ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ CVE-2016-9879 ](https://www.mend.io/vulnerability-database/CVE-2016-9879) | 🔴 High | 8.2 | Not Defined | < 1% | spring-security-web-4.0.2.RELEASE.jar | Direct | 3.2.10,4.1.4,4.2.1. | ✅ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ CVE-2018-1199 ](https://www.mend.io/vulnerability-database/CVE-2018-1199) | 🟠 Medium | 6.9 | Not Defined | 1.5% | spring-security-core-4.0.2.RELEASE.jar | Transitive | N/A | ❌ | |
| [ CVE-2019-11272 ](https://www.mend.io/vulnerability-database/CVE-2019-11272) | 🟠 Medium | 6.9 | Not Defined | < 1% | spring-security-core-4.0.2.RELEASE.jar | Transitive | N/A | ❌ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ WS-2017-3767 ](https://www.mend.io/vulnerability-database/WS-2017-3767) | 🟠 Medium | 6.6 | N/A | N/A | spring-security-web-4.0.2.RELEASE.jar | Direct | N/A | ❌ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ WS-2016-7107 ](https://www.mend.io/vulnerability-database/WS-2016-7107) | 🟠 Medium | 5.9 | N/A | N/A | spring-security-web-4.0.2.RELEASE.jar | Direct | N/A | ❌ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |
| [ WS-2020-0293 ](https://www.mend.io/vulnerability-database/WS-2020-0293) | 🟠 Medium | 5.9 | N/A | N/A | spring-security-web-4.0.2.RELEASE.jar | Direct | N/A | ❌ |<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=20 height=22> Reachable |


# Details


<details>
  <summary>
 🟣CVE-2022-22978
  </summary>

### Vulnerable Library - **spring-security-core-4.0.2.RELEASE.jar**

spring-security-core

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/4.0.2.RELEASE/spring-security-core-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- spring-security-web-4.0.2.RELEASE.jar (Root Library)
    - ❌  **spring-security-core-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Vulnerability Details

In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with "." in the regular expression are possibly vulnerable to an authorization bypass.

**Publish Date:** May 19, 2022 12:00 AM

**URL:** [ CVE-2022-22978 ](https://www.mend.io/vulnerability-database/CVE-2022-22978)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:90.8%

**Score:** 9.3


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://github.com/advisories/GHSA-hh32-7344-cg2f

**Release Date:** May 19, 2022 12:00 AM

**Fix Resolution :** org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-core:5.6.4,org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.6.4,https://github.com/spring-projects/spring-security.git - no_fix


</details>

<details>
  <summary>
 🟣CVE-2022-22978
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder (Extension)
            - org.springframework.security.config.annotation.AbstractConfiguredSecurityBuilder$BuildState (Extension)
                - org.springframework.security.config.annotation.web.builders.HttpSecurity (Extension)
                    -> ❌ org.springframework.security.web.util.matcher.RegexRequestMatcher (Vulnerable Component)
```
***

### Vulnerability Details

In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with "." in the regular expression are possibly vulnerable to an authorization bypass.

**Publish Date:** May 19, 2022 12:00 AM

**URL:** [ CVE-2022-22978 ](https://www.mend.io/vulnerability-database/CVE-2022-22978)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:90.8%

**Score:** 9.3


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://github.com/advisories/GHSA-hh32-7344-cg2f

**Release Date:** May 19, 2022 12:00 AM

**Fix Resolution :** org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-core:5.6.4,org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.6.4,https://github.com/spring-projects/spring-security.git - no_fix


</details>

<details>
  <summary>
 🔴CVE-2016-5007
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder (Extension)
            - org.springframework.security.config.annotation.AbstractConfiguredSecurityBuilder$BuildState (Extension)
                - org.springframework.security.config.annotation.web.builders.HttpSecurity (Extension)
                    - org.springframework.security.config.annotation.web.configurers.ExpressionUrlAuthorizationConfigurer (Extension)
                        -> ❌ org.springframework.security.web.access.expression.ExpressionBasedFilterInvocationSecurityMetadataSource (Vulnerable Component)
```
***

### Vulnerability Details

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.

**Publish Date:** May 25, 2017 05:00 PM

**URL:** [ CVE-2016-5007 ](https://www.mend.io/vulnerability-database/CVE-2016-5007)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:< 1%

**Score:** 8.7


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://pivotal.io/security/cve-2016-5007

**Release Date:** May 25, 2017 05:00 PM

**Fix Resolution :** org.springframework:spring-webmvc:4.3.0.RELEASE,org.springframework.security:spring-security-web:4.1.1.RELEASE,org.springframework.security:spring-security-config:4.1.1.RELEASE


</details>

<details>
  <summary>
 🔴CVE-2020-5407
  </summary>

### Vulnerable Library - **spring-security-core-4.0.2.RELEASE.jar**

spring-security-core

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/4.0.2.RELEASE/spring-security-core-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- spring-security-web-4.0.2.RELEASE.jar (Root Library)
    - ❌  **spring-security-core-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Vulnerability Details

Spring Security versions 5.2.x prior to 5.2.4 and 5.3.x prior to 5.3.2 contain a signature wrapping vulnerability during SAML response validation. When using the spring-security-saml2-service-provider component, a malicious user can carefully modify an otherwise valid SAML response and append an arbitrary assertion that Spring Security will accept as valid.

**Publish Date:** May 13, 2020 05:00 PM

**URL:** [ CVE-2020-5407 ](https://www.mend.io/vulnerability-database/CVE-2020-5407)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:< 1%

**Score:** 8.7


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://osv.dev/vulnerability/CVE-2020-5407

**Release Date:** May 13, 2020 05:00 PM

**Fix Resolution :** https://github.com/spring-projects/spring-security.git - no_fix


</details>

<details>
  <summary>
 🔴CVE-2021-22112
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
            - org.springframework.security.config.annotation.web.configurers.SecurityContextConfigurer (Extension)
                -> ❌ org.springframework.security.web.context.HttpSessionSecurityContextRepository (Vulnerable Component)
```
***

### Vulnerability Details

Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.

**Publish Date:** Feb 23, 2021 06:48 PM

**URL:** [ CVE-2021-22112 ](https://www.mend.io/vulnerability-database/CVE-2021-22112)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:1.0%

**Score:** 8.7


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://github.com/advisories/GHSA-gq28-h5vg-8prx

**Release Date:** Feb 23, 2021 06:48 PM

**Fix Resolution :** org.springframework.security:spring-security-bom:5.4.4,org.springframework.security:spring-security-web:5.4.4,https://github.com/spring-projects/spring-security.git - no_fix


</details>

<details>
  <summary>
 🔴CVE-2016-9879
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
            - org.springframework.security.config.annotation.web.builders.WebSecurity (Extension)
                - org.springframework.security.web.FilterChainProxy (Extension)
                    -> ❌ org.springframework.security.web.firewall.DefaultHttpFirewall (Vulnerable Component)
```
***

### Vulnerability Details

An issue was discovered in Pivotal Spring Security before 3.2.10, 4.1.x before 4.1.4, and 4.2.x before 4.2.1. Spring Security does not consider URL path parameters when processing security constraints. By adding a URL path parameter with an encoded "/" to a request, 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. The unexpected presence of path parameters can cause a constraint to be bypassed. Users of Apache Tomcat (all current versions) are not affected by this vulnerability since Tomcat follows the guidance previously provided by the Servlet Expert group and strips path parameters from the value returned by getContextPath(), getServletPath(), and getPathInfo(). Users of other Servlet containers based on Apache Tomcat may or may not be affected depending on whether or not the handling of path parameters has been modified. Users of IBM WebSphere Application Server 8.5.x are known to be affected. Users of other containers that implement the Servlet specification may be affected.
 Mend Note: The CWE references of this vulnerability differs from MITRE

**Publish Date:** Jan 06, 2017 10:00 PM

**URL:** [ CVE-2016-9879 ](https://www.mend.io/vulnerability-database/CVE-2016-9879)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:< 1%

**Score:** 8.2


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9879

**Release Date:** Jan 06, 2017 10:00 PM

**Fix Resolution :** 3.2.10,4.1.4,4.2.1.


</details>

<details>
  <summary>
 🟠CVE-2018-1199
  </summary>

### Vulnerable Library - **spring-security-core-4.0.2.RELEASE.jar**

spring-security-core

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/4.0.2.RELEASE/spring-security-core-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- spring-security-web-4.0.2.RELEASE.jar (Root Library)
    - ❌  **spring-security-core-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Vulnerability Details

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.

**Publish Date:** Mar 16, 2018 08:00 PM

**URL:** [ CVE-2018-1199 ](https://www.mend.io/vulnerability-database/CVE-2018-1199)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:1.5%

**Score:** 6.9


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1199

**Release Date:** Mar 16, 2018 08:00 PM

**Fix Resolution :** org.springframework.security:spring-security-web:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE;org.springframework.security:spring-security-config:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE;org.springframework:spring-core:4.3.14.RELEASE,5.0.3.RELEASE


</details>

<details>
  <summary>
 🟠CVE-2019-11272
  </summary>

### Vulnerable Library - **spring-security-core-4.0.2.RELEASE.jar**

spring-security-core

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-core/4.0.2.RELEASE/spring-security-core-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- spring-security-web-4.0.2.RELEASE.jar (Root Library)
    - ❌  **spring-security-core-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder (Extension)
            - org.springframework.security.config.annotation.authentication.configurers.ldap.LdapAuthenticationProviderConfigurer (Extension)
                -> ❌ org.springframework.security.authentication.encoding.PlaintextPasswordEncoder (Vulnerable Component)
```
***

### Vulnerability Details

Spring Security, versions 4.2.x up to 4.2.12, and older unsupported versions support plain text passwords using PlaintextPasswordEncoder. If an application using an affected version of Spring Security is leveraging PlaintextPasswordEncoder and a user has a null encoded password, a malicious user (or attacker) can authenticate using a password of "null".

**Publish Date:** Jun 26, 2019 02:06 PM

**URL:** [ CVE-2019-11272 ](https://www.mend.io/vulnerability-database/CVE-2019-11272)

**Threat Assessment**

Exploit Maturity:Not Defined

EPSS:< 1%

**Score:** 6.9


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** 

**Release Date:** 

**Fix Resolution :** 


</details>

<details>
  <summary>
 🟠WS-2017-3767
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder (Extension)
            - org.springframework.security.config.annotation.AbstractConfiguredSecurityBuilder$BuildState (Extension)
                - org.springframework.security.config.annotation.web.builders.HttpSecurity (Extension)
                    - org.springframework.security.config.annotation.web.builders.FilterComparator (Extension)
                        -> ❌ org.springframework.security.web.authentication.switchuser.SwitchUserFilter (Vulnerable Component)
```
***

### Vulnerability Details

Cross-Site Request Forgery (CSRF) vulnerability was found in spring-security before 4.2.15, 5.0.15, 5.1.9, 5.2.3, and 5.3.1. SwitchUserFilter responds to all HTTP methods, making it vulnerable to CSRF attacks.

**Publish Date:** Jan 03, 2017 12:00 AM

**URL:** [ WS-2017-3767 ](https://www.mend.io/vulnerability-database/WS-2017-3767)

**Threat Assessment**

Exploit Maturity:N/A

EPSS:N/A

**Score:** 6.6


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** 

**Release Date:** 

**Fix Resolution :** 


</details>

<details>
  <summary>
 🟠WS-2016-7107
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
            - org.springframework.security.config.annotation.web.configurers.LogoutConfigurer (Extension)
                -> ❌ org.springframework.security.web.authentication.logout.CookieClearingLogoutHandler (Vulnerable Component)
```
***

### Vulnerability Details

CSRF tokens in Spring Security through 5.4.6 are vulnerable to a breach attack. Spring Security always returns the same CSRF token to the browser.

**Publish Date:** Aug 02, 2016 12:00 AM

**URL:** [ WS-2016-7107 ](https://www.mend.io/vulnerability-database/WS-2016-7107)

**Threat Assessment**

Exploit Maturity:N/A

EPSS:N/A

**Score:** 5.9


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** 

**Release Date:** 

**Fix Resolution :** 


</details>

<details>
  <summary>
 🟠WS-2020-0293
  </summary>

### Vulnerable Library - **spring-security-web-4.0.2.RELEASE.jar**

spring-security-web

**Library home page:** [ http://spring.io/spring-security ](http://spring.io/spring-security)

**Path to dependency file:** /pom.xml

**Path to vulnerable library:** /home/wss-scanner/.m2/repository/org/springframework/security/spring-security-web/4.0.2.RELEASE/spring-security-web-4.0.2.RELEASE.jar



**Dependency Hierarchy:**


- ❌  **spring-security-web-4.0.2.RELEASE.jar** (Vulnerable Library)




***

### Reachability Analysis
This vulnerability is potentially reachable:

```
- com.visualpathit.account.service.UserDetailsServiceImpl (Application)
    - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$UserDetailsServiceDelegator (Extension)
        - org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter (Extension)
            - org.springframework.security.config.annotation.web.builders.HttpSecurity (Extension)
                - org.springframework.security.config.annotation.web.builders.FilterComparator (Extension)
                    -> ❌ org.springframework.security.web.csrf.CsrfFilter (Vulnerable Component)
```
***

### Vulnerability Details

Spring Security before 5.2.9, 5.3.7, and 5.4.3 vulnerable to side-channel attacks. Vulnerable versions of Spring Security don't use constant time comparisons for CSRF tokens.

**Publish Date:** Dec 17, 2020 12:00 AM

**URL:** [ WS-2020-0293 ](https://www.mend.io/vulnerability-database/WS-2020-0293)

**Threat Assessment**

Exploit Maturity:N/A

EPSS:N/A

**Score:** 5.9


***
### Suggested Fix

**Type:** Upgrade version

**Origin:** 

**Release Date:** 

**Fix Resolution :** 


</details>

[comment]: <> (<MEND_ISSUE_METADATA>{"identifier":"spring-security-web-4.0.2.RELEASE.jar","repoName":"vprofile-project","branchName":"vp-rem","type":"SCA_DEP"}</MEND_ISSUE_METADATA>)

Finding	Severity	🎯 CVSS	Exploit Maturity	EPSS	Library	Type	Fixed in	Remediation Available	Reachability
CVE-2022-22978	🟣 Critical	9.3	Not Defined	90.8%	spring-security-core-4.0.2.RELEASE.jar	Transitive	N/A	❌
CVE-2022-22978	🟣 Critical	9.3	Not Defined	90.8%	spring-security-web-4.0.2.RELEASE.jar	Direct	org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-core:5.6.4,org.springframework.security:spring-security-web:5.5.7,org.springframework.security:spring-security-web:5.4.11,org.springframework.security:spring-security-web:5.6.4,org.springframework.security:spring-security-core:5.4.11,org.springframework.security:spring-security-core:5.5.7,org.springframework.security:spring-security-core:5.6.4,https://github.com/spring-projects/spring-security.git - no_fix	✅	Reachable
CVE-2016-5007	🔴 High	8.7	Not Defined	< 1%	spring-security-web-4.0.2.RELEASE.jar	Direct	org.springframework:spring-webmvc:4.3.0.RELEASE,org.springframework.security:spring-security-web:4.1.1.RELEASE,org.springframework.security:spring-security-config:4.1.1.RELEASE	✅	Reachable
CVE-2020-5407	🔴 High	8.7	Not Defined	< 1%	spring-security-core-4.0.2.RELEASE.jar	Transitive	N/A	❌
CVE-2021-22112	🔴 High	8.7	Not Defined	1.0%	spring-security-web-4.0.2.RELEASE.jar	Direct	org.springframework.security:spring-security-bom:5.4.4,org.springframework.security:spring-security-web:5.4.4,https://github.com/spring-projects/spring-security.git - no_fix	✅	Reachable
CVE-2016-9879	🔴 High	8.2	Not Defined	< 1%	spring-security-web-4.0.2.RELEASE.jar	Direct	3.2.10,4.1.4,4.2.1.	✅	Reachable
CVE-2018-1199	🟠 Medium	6.9	Not Defined	1.5%	spring-security-core-4.0.2.RELEASE.jar	Transitive	N/A	❌
CVE-2019-11272	🟠 Medium	6.9	Not Defined	< 1%	spring-security-core-4.0.2.RELEASE.jar	Transitive	N/A	❌	Reachable
WS-2017-3767	🟠 Medium	6.6	N/A	N/A	spring-security-web-4.0.2.RELEASE.jar	Direct	N/A	❌	Reachable
WS-2016-7107	🟠 Medium	5.9	N/A	N/A	spring-security-web-4.0.2.RELEASE.jar	Direct	N/A	❌	Reachable
WS-2020-0293	🟠 Medium	5.9	N/A	N/A	spring-security-web-4.0.2.RELEASE.jar	Direct	N/A	❌	Reachable

spring-security-web-4.0.2.RELEASE.jar: 11 vulnerabilities (highest severity is: 9.3) [vp-rem] (reachable) #262

Description

Findings

Details

Vulnerable Library - spring-security-core-4.0.2.RELEASE.jar

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-core-4.0.2.RELEASE.jar

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-core-4.0.2.RELEASE.jar

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-core-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Vulnerable Library - spring-security-web-4.0.2.RELEASE.jar

Reachability Analysis

Vulnerability Details

Suggested Fix

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions