spring-boot-starter-security-2.2.6.RELEASE.jar: 4 vulnerabilities (highest severity is: 8.8) - autoclosed

[dev-mend-for-github-com]

Vulnerable Library - spring-boot-starter-security-2.2.6.RELEASE.jar

Path to dependency file: /tmp/ws-scm/Maven-repo/backend/pom.xml

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

Found in HEAD commit: f751eb4f423c961f1716f7bb99cdf2c487d23044

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in	Remediation Available
CVE-2021-22112	High	8.8	spring-security-web-5.2.2.RELEASE.jar	Transitive	2.3.0.RELEASE	✅
WS-2017-3767	Medium	6.6	spring-security-web-5.2.2.RELEASE.jar	Transitive	2.2.7.RELEASE	✅
WS-2016-7107	Medium	5.9	spring-security-web-5.2.2.RELEASE.jar	Transitive	2.3.0.RELEASE	✅
WS-2020-0293	Medium	5.9	spring-security-web-5.2.2.RELEASE.jar	Transitive	2.3.0.RELEASE	✅

Details

CVE-2021-22112

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

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /tmp/ws-scm/Maven-repo/backend/pom.xml

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

Dependency Hierarchy:

• spring-boot-starter-security-2.2.6.RELEASE.jar (Root Library)
  • ❌ spring-security-web-5.2.2.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: f751eb4f423c961f1716f7bb99cdf2c487d23044

Found in base branch: main

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: 2021-02-23

URL: CVE-2021-22112

CVSS 3 Score Details (8.8)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://tanzu.vmware.com/security/cve-2021-22112

Release Date: 2021-02-23

Fix Resolution (org.springframework.security:spring-security-web): 5.2.9.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-security): 2.3.0.RELEASE

⛑️ Automatic Remediation is available for this issue

WS-2017-3767

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

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /tmp/ws-scm/Maven-repo/backend/pom.xml

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

Dependency Hierarchy:

• spring-boot-starter-security-2.2.6.RELEASE.jar (Root Library)
  • ❌ spring-security-web-5.2.2.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: f751eb4f423c961f1716f7bb99cdf2c487d23044

Found in base branch: main

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: 2017-01-03

URL: WS-2017-3767

CVSS 3 Score Details (6.6)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/spring-projects/spring-security/releases/tag/5.3.1.RELEASE

Release Date: 2017-01-03

Fix Resolution (org.springframework.security:spring-security-web): 5.2.3.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-security): 2.2.7.RELEASE

⛑️ Automatic Remediation is available for this issue

WS-2016-7107

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

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /tmp/ws-scm/Maven-repo/backend/pom.xml

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

Dependency Hierarchy:

• spring-boot-starter-security-2.2.6.RELEASE.jar (Root Library)
  • ❌ spring-security-web-5.2.2.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: f751eb4f423c961f1716f7bb99cdf2c487d23044

Found in base branch: main

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: 2016-08-02

URL: WS-2016-7107

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://nvd.nist.gov/vuln/detail/WS-2016-7107

Release Date: 2016-08-02

Fix Resolution (org.springframework.security:spring-security-web): 5.2.11.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-security): 2.3.0.RELEASE

⛑️ Automatic Remediation is available for this issue

WS-2020-0293

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

spring-security-web

Library home page: http://spring.io/spring-security

Path to dependency file: /tmp/ws-scm/Maven-repo/backend/pom.xml

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

Dependency Hierarchy:

• spring-boot-starter-security-2.2.6.RELEASE.jar (Root Library)
  • ❌ spring-security-web-5.2.2.RELEASE.jar (Vulnerable Library)

Found in HEAD commit: f751eb4f423c961f1716f7bb99cdf2c487d23044

Found in base branch: main

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: 2020-12-17

URL: WS-2020-0293

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: spring-projects/spring-security#9291

Release Date: 2020-12-17

Fix Resolution (org.springframework.security:spring-security-web): 5.2.9.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-security): 2.3.0.RELEASE

⛑️ Automatic Remediation is available for this issue

---

⛑️ Automatic Remediation is available for this issue.

[dev-mend-for-github-com]

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.

[dev-mend-for-github-com]

ℹ️ This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.

[dev-mend-for-github-com]

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.