zinc_2.13-1.6.1.jar: 2 vulnerabilities (highest severity is: 9.2) unreachable

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

Vulnerable Library - zinc_2.13-1.6.1.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/jline/jline/3.19.0/jline-3.19.0.jar

Found in HEAD commit: 0535b00e652a49146dbe0273d6dfa6ec16b74c8f

Vulnerabilities

CVE	Severity	CVSS	Exploit Maturity	EPSS	Dependency	Type	Fixed in (zinc_2.13 version)	Remediation Possible**	Reachability
CVE-2022-36944	Critical	9.2	Not Defined	0.8%	scala-library-2.13.6.jar	Transitive	N/A*	❌	Unreachable
CVE-2023-50572	Medium	6.8	Not Defined	0.0%	jline-3.19.0.jar	Transitive	1.10.2	✅	Unreachable

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

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

Details

CVE-2022-36944

### Vulnerable Library - scala-library-2.13.6.jar

Standard library for the Scala Programming Language

Library home page: https://www.scala-lang.org/

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/scala-lang/scala-library/2.13.6/scala-library-2.13.6.jar

Dependency Hierarchy: - zinc_2.13-1.6.1.jar (Root Library) - :x: **scala-library-2.13.6.jar** (Vulnerable Library)

Found in HEAD commit: 0535b00e652a49146dbe0273d6dfa6ec16b74c8f

Found in base branch: master

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

Scala 2.13.x before 2.13.9 has a Java deserialization chain in its JAR file. On its own, it cannot be exploited. There is only a risk in conjunction with Java object deserialization within an application. In such situations, it allows attackers to erase contents of arbitrary files, make network connections, or possibly run arbitrary code (specifically, Function0 functions) via a gadget chain.

Publish Date: 2022-09-23

URL: CVE-2022-36944

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.8%

### CVSS 4 Score Details (9.2)

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

For more information on CVSS4 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2022-09-23

Fix Resolution: org.scala-lang:scala-library:2.13.9

CVE-2023-50572

### Vulnerable Library - jline-3.19.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/jline/jline/3.19.0/jline-3.19.0.jar

Dependency Hierarchy: - zinc_2.13-1.6.1.jar (Root Library) - zinc-core_2.13-1.6.1.jar - zinc-compile-core_2.13-1.6.1.jar - zinc-classpath_2.13-1.6.1.jar - scala-compiler-2.13.6.jar - :x: **jline-3.19.0.jar** (Vulnerable Library)

Found in HEAD commit: 0535b00e652a49146dbe0273d6dfa6ec16b74c8f

Found in base branch: master

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

An issue in the component GroovyEngine.execute of jline-groovy v3.24.1 allows attackers to cause an OOM (OutofMemory) error.

Publish Date: 2023-12-29

URL: CVE-2023-50572

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.0%

### CVSS 4 Score Details (6.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A

For more information on CVSS4 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2023-12-29

Fix Resolution (org.jline:jline): 3.25.0

Direct dependency fix Resolution (org.scala-sbt:zinc_2.13): 1.10.2

In order to enable automatic remediation, please create workflow rules

---

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