CVE-2020-10693 (Medium) detected in hibernate-validator-5.2.5.Final.jar

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

CVE-2020-10693 - Medium Severity Vulnerability

Vulnerable Library - hibernate-validator-5.2.5.Final.jar

Hibernate's Bean Validation (JSR-303) reference implementation.

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

Path to dependency file: /operation-expert/pom.xml

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

Dependency Hierarchy: - spring-boot-starter-hateoas-1.4.7.RELEASE.jar (Root Library) - spring-boot-starter-web-1.4.7.RELEASE.jar - :x: **hibernate-validator-5.2.5.Final.jar** (Vulnerable Library)

Found in HEAD commit: dd01a1d4381c7a3b94ba25748c015a094c33088e

Found in base branch: master

Vulnerability Details

A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.

Publish Date: 2020-05-06

URL: CVE-2020-10693

CVSS 3 Score Details (5.3)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://in.relation.to/2020/05/07/hibernate-validator-615-6020-released/

Release Date: 2020-05-06

Fix Resolution (org.hibernate:hibernate-validator): 6.0.0.Alpha1

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-hateoas): 2.0.0.RELEASE

---

• [ ] Check this box to open an automated fix PR

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

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

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

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

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