Uncleken13 / easybuggy

Too buggy web application
Apache License 2.0
0 stars 0 forks source link

xalan-2.7.0.jar: 2 vulnerabilities (highest severity is: 7.5) #8

Open mend-for-github-com[bot] opened 1 year ago

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

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar,/target/easybuggy-1-SNAPSHOT/WEB-INF/lib/xalan-2.7.0.jar

Found in HEAD commit: 93e09a67edcb1d13739f2d1e92a4d467fc5a5406

Vulnerabilities

CVE Severity CVSS Exploit Maturity EPSS Dependency Type Fixed in (xalan version) Remediation Possible** Reachability
CVE-2022-34169 High 7.5 Not Defined 0.2% xalan-2.7.0.jar Direct xalan:xalan:2.7.3
CVE-2014-0107 High 7.3 Not Defined 0.5% xalan-2.7.0.jar Direct 2.7.2

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

Details

CVE-2022-34169 ### Vulnerable Library - xalan-2.7.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar,/target/easybuggy-1-SNAPSHOT/WEB-INF/lib/xalan-2.7.0.jar

Dependency Hierarchy: - :x: **xalan-2.7.0.jar** (Vulnerable Library)

Found in HEAD commit: 93e09a67edcb1d13739f2d1e92a4d467fc5a5406

Found in base branch: master

### Vulnerability Details

The Apache Xalan Java XSLT library is vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. This can be used to corrupt Java class files generated by the internal XSLTC compiler and execute arbitrary Java bytecode. Users are recommended to update to version 2.7.3 or later. Note: Java runtimes (such as OpenJDK) include repackaged copies of Xalan.

Publish Date: 2022-07-19

URL: CVE-2022-34169

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.2%

### 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: High - Availability Impact: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-9339-86wc-4qgf

Release Date: 2022-07-19

Fix Resolution: xalan:xalan:2.7.3

In order to enable automatic remediation, please create workflow rules

CVE-2014-0107 ### Vulnerable Library - xalan-2.7.0.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/xalan/xalan/2.7.0/xalan-2.7.0.jar,/target/easybuggy-1-SNAPSHOT/WEB-INF/lib/xalan-2.7.0.jar

Dependency Hierarchy: - :x: **xalan-2.7.0.jar** (Vulnerable Library)

Found in HEAD commit: 93e09a67edcb1d13739f2d1e92a4d467fc5a5406

Found in base branch: master

### Vulnerability Details

The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

Publish Date: 2014-04-15

URL: CVE-2014-0107

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.5%

### CVSS 3 Score Details (7.3)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0107

Release Date: 2014-04-15

Fix Resolution: 2.7.2

In order to enable automatic remediation, please create workflow rules


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