spring-boot-gradle-plugin-2.2.11.RELEASE.jar: 3 vulnerabilities (highest severity is: 5.3)

[mend-for-jackfan.us.kg]

Vulnerable Library - spring-boot-gradle-plugin-2.2.11.RELEASE.jar

Path to dependency file: /jib-gradle-plugin/build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.2.10.RELEASE/29423e9f1d766eb4f4e3516211877f361fe3169f/spring-core-5.2.10.RELEASE.jar

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (spring-boot-gradle-plugin version)	Remediation Possible**	Reachability
CVE-2022-22970	Medium	5.3	spring-core-5.2.10.RELEASE.jar	Transitive	2.3.0.RELEASE	✅
CVE-2021-22096	Medium	4.3	spring-core-5.2.10.RELEASE.jar	Transitive	2.3.0.RELEASE	✅
CVE-2021-22060	Medium	4.3	spring-core-5.2.10.RELEASE.jar	Transitive	2.3.0.RELEASE	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2022-22970

Vulnerable Library - spring-core-5.2.10.RELEASE.jar

Spring Core

Library home page: https://spring.io/projects/spring-framework

Path to dependency file: /jib-gradle-plugin/build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.2.10.RELEASE/29423e9f1d766eb4f4e3516211877f361fe3169f/spring-core-5.2.10.RELEASE.jar

Dependency Hierarchy:

• spring-boot-gradle-plugin-2.2.11.RELEASE.jar (Root Library)
  • spring-boot-loader-tools-2.2.11.RELEASE.jar
    • ❌ spring-core-5.2.10.RELEASE.jar (Vulnerable Library)

Found in base branch: master

Vulnerability Details

In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.

Publish Date: 2022-05-12

URL: CVE-2022-22970

CVSS 3 Score Details (5.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://tanzu.vmware.com/security/cve-2022-22970

Release Date: 2022-05-12

Fix Resolution (org.springframework:spring-core): 5.2.22.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-gradle-plugin): 2.3.0.RELEASE

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2021-22096

Vulnerable Library - spring-core-5.2.10.RELEASE.jar

Spring Core

Library home page: https://spring.io/projects/spring-framework

Path to dependency file: /jib-gradle-plugin/build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.2.10.RELEASE/29423e9f1d766eb4f4e3516211877f361fe3169f/spring-core-5.2.10.RELEASE.jar

Dependency Hierarchy:

• spring-boot-gradle-plugin-2.2.11.RELEASE.jar (Root Library)
  • spring-boot-loader-tools-2.2.11.RELEASE.jar
    • ❌ spring-core-5.2.10.RELEASE.jar (Vulnerable Library)

Found in base branch: master

Vulnerability Details

In Spring Framework versions 5.3.0 - 5.3.10, 5.2.0 - 5.2.17, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries.

Publish Date: 2021-10-28

URL: CVE-2021-22096

CVSS 3 Score Details (4.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

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

Release Date: 2021-10-28

Fix Resolution (org.springframework:spring-core): 5.2.18.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-gradle-plugin): 2.3.0.RELEASE

⛑️ Automatic Remediation will be attempted for this issue.

CVE-2021-22060

Vulnerable Library - spring-core-5.2.10.RELEASE.jar

Spring Core

Library home page: https://spring.io/projects/spring-framework

Path to dependency file: /jib-gradle-plugin/build.gradle

Path to vulnerable library: /tmp/containerbase/cache/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.2.10.RELEASE/29423e9f1d766eb4f4e3516211877f361fe3169f/spring-core-5.2.10.RELEASE.jar

Dependency Hierarchy:

• spring-boot-gradle-plugin-2.2.11.RELEASE.jar (Root Library)
  • spring-boot-loader-tools-2.2.11.RELEASE.jar
    • ❌ spring-core-5.2.10.RELEASE.jar (Vulnerable Library)

Found in base branch: master

Vulnerability Details

In Spring Framework versions 5.3.0 - 5.3.13, 5.2.0 - 5.2.18, and older unsupported versions, it is possible for a user to provide malicious input to cause the insertion of additional log entries. This is a follow-up to CVE-2021-22096 that protects against additional types of input and in more places of the Spring Framework codebase.

Publish Date: 2022-01-07

URL: CVE-2021-22060

CVSS 3 Score Details (4.3)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://spring.io/security/cve-2021-22060

Release Date: 2022-01-07

Fix Resolution (org.springframework:spring-core): 5.2.19.RELEASE

Direct dependency fix Resolution (org.springframework.boot:spring-boot-gradle-plugin): 2.3.0.RELEASE

⛑️ Automatic Remediation will be attempted for this issue.

---

⛑️Automatic Remediation will be attempted for this issue.

[mend-for-jackfan.us.kg]

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

[mend-for-jackfan.us.kg]

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