Privilege Escalation in Hibernate Validator
Red Hat, Inc. hibernate-validator
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.hibernate:hibernate-validator Maven |
|
|
Red Hat, Inc. hibernate-validator
| Product | Affected | Fixed in |
|---|---|---|
| org.hibernate:hibernate-validator Maven |
|
|
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().
From the CVE record · redhat
Hibernate Validator can expose a private member value through ConstraintViolation#getInvalidValue() when it has been granted reflective permissions by the security manager. An attacker who can validate an invalid instance may access that value without having the permission themselves, potentially escalating privileges. The input does not specify whether network access, authentication, or user interaction is required.
Check applications using Maven org.hibernate:hibernate-validator versions >=5.2.0 <5.2.5.Final, >=5.3.0 <5.3.6.Final, or >=5.4.0 <5.4.2.Final.