spring-boot-starter-actuator-2.7.1.jar: 2 vulnerabilities (highest severity is: 9.8)

[mend-for-github-com[bot]]

Vulnerable Library - spring-boot-starter-actuator-2.7.1.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /pom.xml

Found in HEAD commit: aa225d319bbc2e5a7f67311333ffd522370dca22

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (spring-boot-starter-actuator version)	Remediation Possible**
CVE-2023-20873	Critical	9.8	spring-boot-actuator-autoconfigure-2.7.1.jar	Transitive	2.7.12	✅
CVE-2023-34055	Medium	5.3	spring-boot-actuator-2.7.1.jar	Transitive	2.7.18	✅

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

Details

CVE-2023-20873

### Vulnerable Library - spring-boot-actuator-autoconfigure-2.7.1.jar

Spring Boot Actuator AutoConfigure

Library home page: https://spring.io

Path to dependency file: /pom.xml

Path to vulnerable library: /pom.xml

Dependency Hierarchy: - spring-boot-starter-actuator-2.7.1.jar (Root Library) - :x: **spring-boot-actuator-autoconfigure-2.7.1.jar** (Vulnerable Library)

Found in HEAD commit: aa225d319bbc2e5a7f67311333ffd522370dca22

Found in base branch: main

### Vulnerability Details

In Spring Boot versions 3.0.0 - 3.0.5, 2.7.0 - 2.7.10, and older unsupported versions, an application that is deployed to Cloud Foundry could be susceptible to a security bypass. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.6+. 2.7.x users should upgrade to 2.7.11+. Users of older, unsupported versions should upgrade to 3.0.6+ or 2.7.11+.

Publish Date: 2023-04-20

URL: CVE-2023-20873

### CVSS 3 Score Details (9.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - 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://spring.io/security/cve-2023-20873

Release Date: 2023-04-20

Fix Resolution (org.springframework.boot:spring-boot-actuator-autoconfigure): 2.7.12

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-actuator): 2.7.12

In order to enable automatic remediation, please create workflow rules

CVE-2023-34055

### Vulnerable Library - spring-boot-actuator-2.7.1.jar

Spring Boot Actuator

Library home page: https://spring.io

Path to dependency file: /pom.xml

Path to vulnerable library: /pom.xml

Dependency Hierarchy: - spring-boot-starter-actuator-2.7.1.jar (Root Library) - spring-boot-actuator-autoconfigure-2.7.1.jar - :x: **spring-boot-actuator-2.7.1.jar** (Vulnerable Library)

Found in HEAD commit: aa225d319bbc2e5a7f67311333ffd522370dca22

Found in base branch: main

### Vulnerability Details

In Spring Boot versions 2.7.0 - 2.7.17, 3.0.0-3.0.12 and 3.1.0-3.1.5, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition. Specifically, an application is vulnerable when all of the following are true: * the application uses Spring MVC or Spring WebFlux * org.springframework.boot:spring-boot-actuator is on the classpath

Publish Date: 2023-11-28

URL: CVE-2023-34055

### CVSS 3 Score Details (5.3)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://spring.io/security/cve-2023-34055

Release Date: 2023-11-28

Fix Resolution (org.springframework.boot:spring-boot-actuator): 2.7.18

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-actuator): 2.7.18

In order to enable automatic remediation, please create workflow rules

---

In order to enable automatic remediation for this issue, please create workflow rules