AlexRogalskiy / java4you

The AlpenidOs project
MIT License
0 stars 0 forks source link

CVE-2020-25638 (High) detected in hibernate-core-5.4.2.Final.jar - autoclosed #64

Closed mend-bolt-for-github[bot] closed 3 years ago

mend-bolt-for-github[bot] commented 3 years ago

CVE-2020-25638 - High Severity Vulnerability

Vulnerable Library - hibernate-core-5.4.2.Final.jar

Hibernate's core ORM functionality

Library home page: http://hibernate.org/orm

Path to dependency file: java4you/pom.xml

Path to vulnerable library: 20210131175039_ODYKXS/downloadResource_HOMULE/20210131175852/hibernate-core-5.4.2.Final.jar

Dependency Hierarchy: - :x: **hibernate-core-5.4.2.Final.jar** (Vulnerable Library)

Found in HEAD commit: d7e409b73576f85ef958df67617ad1342a9e53d1

Found in base branch: master

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,5.4.24.Final


Step up your Open Source Security Game with WhiteSource here

mend-bolt-for-github[bot] commented 3 years ago

:information_source: This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #66