amaybaum-prod / vprofile-project

0 stars 2 forks source link

hibernate-entitymanager-4.3.11.Final.jar: 4 vulnerabilities (highest severity is: 9.8) unreachable #27

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

mend-for-github-com[bot] commented 1 year ago
Vulnerable Library - hibernate-entitymanager-4.3.11.Final.jar

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (hibernate-entitymanager version) Remediation Possible** Reachability
CVE-2020-10683 Critical 9.8 dom4j-1.6.1.jar Transitive 5.0.2.Final

Unreachable

CVE-2018-1000632 High 7.5 dom4j-1.6.1.jar Transitive 5.0.2.Final

Unreachable

CVE-2020-25638 High 7.4 hibernate-core-4.3.11.Final.jar Transitive 5.0.2.Final

Unreachable

CVE-2019-14900 Medium 6.5 hibernate-core-4.3.11.Final.jar Transitive 5.0.2.Final

Unreachable

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

Details

CVE-2020-10683 ### Vulnerable Library - dom4j-1.6.1.jar

dom4j: the flexible XML framework for Java

Library home page: http://sourceforge.net/projects/dom4j

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar

Dependency Hierarchy: - hibernate-entitymanager-4.3.11.Final.jar (Root Library) - hibernate-core-4.3.11.Final.jar - :x: **dom4j-1.6.1.jar** (Vulnerable Library)

Found in base branch: vp-rem

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.

Publish Date: 2020-05-01

URL: CVE-2020-10683

### CVSS 3 Score Details (9.8)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Release Date: 2020-05-01

Fix Resolution (dom4j:dom4j): 20040902.021138

Direct dependency fix Resolution (org.hibernate:hibernate-entitymanager): 5.0.2.Final

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2018-1000632 ### Vulnerable Library - dom4j-1.6.1.jar

dom4j: the flexible XML framework for Java

Library home page: http://sourceforge.net/projects/dom4j

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar

Dependency Hierarchy: - hibernate-entitymanager-4.3.11.Final.jar (Root Library) - hibernate-core-4.3.11.Final.jar - :x: **dom4j-1.6.1.jar** (Vulnerable Library)

Found in base branch: vp-rem

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.

Publish Date: 2018-08-20

URL: CVE-2018-1000632

### 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632/

Release Date: 2018-08-20

Fix Resolution (dom4j:dom4j): 20040902.021138

Direct dependency fix Resolution (org.hibernate:hibernate-entitymanager): 5.0.2.Final

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2020-25638 ### Vulnerable Library - hibernate-core-4.3.11.Final.jar

The core O/RM functionality as provided by Hibernate

Library home page: http://hibernate.org

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/4.3.11.Final/hibernate-core-4.3.11.Final.jar

Dependency Hierarchy: - hibernate-entitymanager-4.3.11.Final.jar (Root Library) - :x: **hibernate-core-4.3.11.Final.jar** (Vulnerable Library)

Found in base branch: vp-rem

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.

Publish Date: 2020-12-02

URL: CVE-2020-25638

### CVSS 3 Score Details (7.4)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/

Release Date: 2020-12-02

Fix Resolution (org.hibernate:hibernate-core): 5.3.20.Final

Direct dependency fix Resolution (org.hibernate:hibernate-entitymanager): 5.0.2.Final

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
CVE-2019-14900 ### Vulnerable Library - hibernate-core-4.3.11.Final.jar

The core O/RM functionality as provided by Hibernate

Library home page: http://hibernate.org

Path to dependency file: /pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/4.3.11.Final/hibernate-core-4.3.11.Final.jar

Dependency Hierarchy: - hibernate-entitymanager-4.3.11.Final.jar (Root Library) - :x: **hibernate-core-4.3.11.Final.jar** (Vulnerable Library)

Found in base branch: vp-rem

### Reachability Analysis

The vulnerable code is unreachable

### Vulnerability Details

A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.

Publish Date: 2020-07-06

URL: CVE-2019-14900

### CVSS 3 Score Details (6.5)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - 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 Fix

Type: Upgrade version

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

Release Date: 2020-07-06

Fix Resolution (org.hibernate:hibernate-core): 5.1.10.Final

Direct dependency fix Resolution (org.hibernate:hibernate-entitymanager): 5.0.2.Final

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.

:rescue_worker_helmet:Automatic Remediation will be attempted 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.

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

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