Open mend-for-github-com[bot] opened 1 year ago
:heavy_check_mark: 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.
:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.
Vulnerable Library - spring-boot-starter-undertow-2.7.1.jar
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/undertow/undertow-core/2.2.18.Final/undertow-core-2.2.18.Final.jar
Found in HEAD commit: 9e6fae155f315fd0f4b7ffb352b78b28e6d061b9
Vulnerabilities
Reachable
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2023-5379
### Vulnerable Library - undertow-core-2.2.18.Final.jarLibrary home page: http://www.jboss.org
Path to dependency file: /pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/io/undertow/undertow-core/2.2.18.Final/undertow-core-2.2.18.Final.jar
Dependency Hierarchy: - spring-boot-starter-undertow-2.7.1.jar (Root Library) - :x: **undertow-core-2.2.18.Final.jar** (Vulnerable Library)
Found in HEAD commit: 9e6fae155f315fd0f4b7ffb352b78b28e6d061b9
Found in base branch: main
### Reachability Analysis This vulnerability is potentially reachable ``` org.owasp.webgoat.container.WebSecurityConfig (Application) -> org.springframework.security.config.annotation.web.configuration.EnableWebSecurity (Extension) -> org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration (Extension) -> org.springframework.boot.autoconfigure.web.servlet.ServletWebServerFactoryAutoConfiguration (Extension) ... -> io.undertow.Undertow (Extension) -> io.undertow.server.protocol.ajp.AjpOpenListener (Extension) -> ❌ io.undertow.server.protocol.ajp.AjpOpenListener$2 (Vulnerable Component) ``` ### Vulnerability DetailsA flaw was found in Undertow. When an AJP request is sent that exceeds the max-header-size attribute in ajp-listener, JBoss EAP is marked in an error state by mod_cluster in httpd, causing JBoss EAP to close the TCP connection without returning an AJP response. This happens because mod_proxy_cluster marks the JBoss EAP instance as an error worker when the TCP connection is closed from the backend after sending the AJP request without receiving an AJP response, and stops forwarding. This issue could allow a malicious user could to repeatedly send requests that exceed the max-header-size, causing a Denial of Service (DoS).
Publish Date: 2023-12-12
URL: CVE-2023-5379
### Threat AssessmentExploit Maturity: Not Defined
EPSS: 0.1%
### 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: High - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Release Date: 2023-12-12
Fix Resolution (io.undertow:undertow-core): 2.2.31.Final
Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-undertow): 3.0.0
In order to enable automatic remediation, please create workflow rules
In order to enable automatic remediation for this issue, please create workflow rules