AlexRogalskiy / ws-documents

WebDocs
GNU General Public License v3.0
2 stars 0 forks source link

CVE-2023-34054 (High) detected in reactor-netty-http-1.0.24.jar #403

Open mend-bolt-for-github[bot] opened 8 months ago

mend-bolt-for-github[bot] commented 8 months ago

CVE-2023-34054 - High Severity Vulnerability

Vulnerable Library - reactor-netty-http-1.0.24.jar

HTTP functionality for the Reactor Netty library

Path to dependency file: /modules/discovery/pom.xml

Path to vulnerable library: /modules/discovery/pom.xml,/modules/all/pom.xml,/modules/eureka/pom.xml

Dependency Hierarchy: - spring-boot-starter-webflux-2.7.5.jar (Root Library) - spring-boot-starter-reactor-netty-2.7.5.jar - :x: **reactor-netty-http-1.0.24.jar** (Vulnerable Library)

Found in HEAD commit: c7ec20e7636517fb8d076d86cdac3414ca4c5842

Found in base branch: master

Vulnerability Details

In Reactor Netty HTTP Server, versions 1.1.x prior to 1.1.13 and versions 1.0.x prior to 1.0.39, 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 if Reactor Netty HTTP Server built-in integration with Micrometer is enabled.

Publish Date: 2023-11-28

URL: CVE-2023-34054

CVSS 3 Score Details (7.5)

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: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

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

Release Date: 2023-11-28

Fix Resolution (io.projectreactor.netty:reactor-netty-http): 1.0.39

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


Step up your Open Source Security Game with Mend here

github-actions[bot] commented 8 months ago

Thank you for opening an issue. If this issue is related to a bug, please follow the steps and provide the information outlined in the Troubleshooting Guide. Failure to follow these instructions may result in automatic closing of this issue.