RSA-Demo / vprofile-project

0 stars 0 forks source link

hibernate-validator-5.2.1.Final.jar: 3 vulnerabilities (highest severity is: 7.0) reachable #18

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

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

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

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

Path to dependency file: /pom.xml

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

Found in HEAD commit: e05a354f76ea8825b79bebaf46a05fc37d1979e0

Vulnerabilities

CVE Severity CVSS Dependency Type Fixed in (hibernate-validator version) Remediation Possible** Reachability
CVE-2017-7536 High 7.0 hibernate-validator-5.2.1.Final.jar Direct 5.3.0.Alpha1

Reachable

CVE-2023-1932 Medium 6.1 hibernate-validator-5.2.1.Final.jar Direct 6.2.0.CR1

Reachable

CVE-2020-10693 Medium 5.3 hibernate-validator-5.2.1.Final.jar Direct 6.0.0.Alpha1

Reachable

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

Details

CVE-2017-7536 ### Vulnerable Library - hibernate-validator-5.2.1.Final.jar

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

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

Path to dependency file: /pom.xml

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

Dependency Hierarchy: - :x: **hibernate-validator-5.2.1.Final.jar** (Vulnerable Library)

Found in HEAD commit: e05a354f76ea8825b79bebaf46a05fc37d1979e0

Found in base branch: vp-rem

### Reachability Analysis This vulnerability is potentially reachable ``` com.visualpathit.account.validator.UserValidator (Application) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean (Extension) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean$HibernateValidatorDelegate (Extension) -> org.hibernate.validator.internal.metadata.core.ConstraintHelper (Extension) ... -> org.hibernate.validator.HibernateValidator (Extension) -> org.hibernate.validator.internal.engine.ValidatorFactoryImpl (Extension) -> ❌ org.hibernate.validator.internal.engine.ValidatorImpl (Vulnerable Component) ```

### Vulnerability Details

In Hibernate Validator 5.2.x before 5.2.5 final, 5.3.x, and 5.4.x, it was found that when the security manager's reflective permissions, which allows it to access the private members of the class, are granted to Hibernate Validator, a potential privilege escalation can occur. By allowing the calling code to access those private members without the permission an attacker may be able to validate an invalid instance and access the private member value via ConstraintViolation#getInvalidValue().

Publish Date: 2018-01-10

URL: CVE-2017-7536

### CVSS 3 Score Details (7.0)

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

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

Release Date: 2017-06-27

Fix Resolution: 5.3.0.Alpha1

In order to enable automatic remediation, please create workflow rules

CVE-2023-1932 ### Vulnerable Library - hibernate-validator-5.2.1.Final.jar

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

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

Path to dependency file: /pom.xml

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

Dependency Hierarchy: - :x: **hibernate-validator-5.2.1.Final.jar** (Vulnerable Library)

Found in HEAD commit: e05a354f76ea8825b79bebaf46a05fc37d1979e0

Found in base branch: vp-rem

### Reachability Analysis This vulnerability is potentially reachable ``` com.visualpathit.account.validator.UserValidator (Application) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean (Extension) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean$HibernateValidatorDelegate (Extension) -> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator (Extension) -> org.hibernate.validator.internal.util.logging.Log (Extension) -> org.hibernate.validator.internal.metadata.descriptor.ConstraintDescriptorImpl (Extension) -> ❌ org.hibernate.validator.internal.metadata.core.ConstraintHelper (Vulnerable Component) ```

### Vulnerability Details

A vulnerability was found in hibernate-validator version 6.1.2.Final, where the method 'isValid' in the class org.hibernate.validator.internal.constraintvalidators.hv.SafeHtmlValidator can by bypassed by omitting the tag end (less than sign). Browsers typically still render the invalid html which leads to attacks like HTML injection and Cross-Site-Scripting.

Publish Date: 2023-04-07

URL: CVE-2023-1932

### CVSS 3 Score Details (6.1)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://bugzilla.redhat.com/show_bug.cgi?id=1809444

Release Date: 2023-04-07

Fix Resolution: 6.2.0.CR1

In order to enable automatic remediation, please create workflow rules

CVE-2020-10693 ### Vulnerable Library - hibernate-validator-5.2.1.Final.jar

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

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

Path to dependency file: /pom.xml

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

Dependency Hierarchy: - :x: **hibernate-validator-5.2.1.Final.jar** (Vulnerable Library)

Found in HEAD commit: e05a354f76ea8825b79bebaf46a05fc37d1979e0

Found in base branch: vp-rem

### Reachability Analysis This vulnerability is potentially reachable ``` com.visualpathit.account.validator.UserValidator (Application) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean (Extension) -> org.springframework.validation.beanvalidation.LocalValidatorFactoryBean$HibernateValidatorDelegate (Extension) -> org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator (Extension) ... -> org.hibernate.validator.internal.engine.messageinterpolation.parser.TokenCollector (Extension) -> org.hibernate.validator.internal.engine.messageinterpolation.parser.BeginState (Extension) -> ❌ org.hibernate.validator.internal.engine.messageinterpolation.parser.MessageState (Vulnerable Component) ```

### 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: 6.0.0.Alpha1

In order to enable automatic remediation, please create workflow rules


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