pferron / Case119044

0 stars 0 forks source link

xstream-1.4.19.jar: 2 vulnerabilities (highest severity is: 7.5) - autoclosed #2

Closed mend-for-github-com[bot] closed 1 year ago

mend-for-github-com[bot] commented 1 year ago
Vulnerable Library - xstream-1.4.19.jar

Library home page: http://x-stream.github.io

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.19/xstream-1.4.19.jar

Found in HEAD commit: a0ebd992d0c504f02b78e7c379b5fd56d11b2323

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (xstream version) Remediation Available
CVE-2022-41966 High 7.5 xstream-1.4.19.jar Direct 1.4.20
CVE-2022-40151 High 7.5 xstream-1.4.19.jar Direct 1.4.20

Details

CVE-2022-41966 ### Vulnerable Library - xstream-1.4.19.jar

Library home page: http://x-stream.github.io

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.19/xstream-1.4.19.jar

Dependency Hierarchy: - :x: **xstream-1.4.19.jar** (Vulnerable Library)

Found in HEAD commit: a0ebd992d0c504f02b78e7c379b5fd56d11b2323

Found in base branch: main

### Vulnerability Details

XStream serializes Java objects to XML and back again. Versions prior to 1.4.20 may allow a remote attacker to terminate the application with a stack overflow error, resulting in a denial of service only via manipulation the processed input stream. The attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow. This issue is patched in version 1.4.20 which handles the stack overflow and raises an InputManipulationException instead. A potential workaround for users who only use HashMap or HashSet and whose XML refers these only as default map or set, is to change the default implementation of java.util.Map and java.util per the code example in the referenced advisory. However, this implies that your application does not care about the implementation of the map and all elements are comparable.

Publish Date: 2022-12-28

URL: CVE-2022-41966

### 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://github.com/advisories/GHSA-j563-grx4-pjpv

Release Date: 2022-12-28

Fix Resolution: 1.4.20

:rescue_worker_helmet: Automatic Remediation is available for this issue
CVE-2022-40151 ### Vulnerable Library - xstream-1.4.19.jar

Library home page: http://x-stream.github.io

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.19/xstream-1.4.19.jar

Dependency Hierarchy: - :x: **xstream-1.4.19.jar** (Vulnerable Library)

Found in HEAD commit: a0ebd992d0c504f02b78e7c379b5fd56d11b2323

Found in base branch: main

### Vulnerability Details

Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.

Publish Date: 2022-09-16

URL: CVE-2022-40151

### 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://github.com/advisories/GHSA-f8cc-g7j8-xxpm

Release Date: 2022-09-16

Fix Resolution: 1.4.20

:rescue_worker_helmet: Automatic Remediation is available for this issue

:rescue_worker_helmet: Automatic Remediation is available for this issue.

mend-for-github-com[bot] commented 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.