First published: Tue Jun 27 2017(Updated: )
A vulnerability which allows for a potential privilege escalation was found in the Hibernate Validator. If a security manager is present and HV itself is allowed to access private members reflectively as per the SM's configuration, that'll allow calling code without that permission to get hold of private state. The attack vector is to declare a constraint on a private member using XML, validate an invalid instance of that type and access the private member value via ConstraintViolation#getInvalidValue().
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/hibernate-validator | <4.3.4. | 4.3.4. |
redhat/hibernate-validator | <5.3.5. | 5.3.5. |
Red Hat Hibernate Validator | >=5.2.0<5.2.5 | |
Red Hat Hibernate Validator | >=5.3.0<5.3.6 | |
Red Hat Hibernate Validator | >=5.4.0<5.4.2 | |
Red Hat Satellite | =6.4 | |
Red Hat Satellite | =6.4 | |
JBoss Enterprise Application Platform | =6.0.0 | |
JBoss Enterprise Application Platform | =6.4.0 | |
Red Hat Enterprise Linux | =5.0 | |
Red Hat Enterprise Linux | =6.0 | |
Red Hat Enterprise Linux | =7.0 | |
JBoss Enterprise Application Platform | =7.0 | |
JBoss Enterprise Application Platform | =7.1 | |
Red Hat Enterprise Virtualization | =4.0 | |
Red Hat Virtualization Host EUS | =4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7536 is classified as a potential privilege escalation vulnerability.
To mitigate CVE-2017-7536, update Hibernate Validator to version 5.3.6 or later.
Hibernate Validator versions prior to 5.3.6 and 4.3.4 are affected by CVE-2017-7536.
Yes, CVE-2017-7536 affects multiple Red Hat products that utilize vulnerable versions of Hibernate Validator.
No, CVE-2017-7536 requires a security manager configured to allow reflective access to private members.