CVE-2017-7536
Published: 10 January 2018
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().
Priority
Status
| Package | Release | Status |
|---|---|---|
|
libhibernate-validator-java Launchpad, Ubuntu, Debian |
artful |
Ignored
(end of life)
|
| bionic |
Not vulnerable
(4.3.3-4)
|
|
| cosmic |
Not vulnerable
(4.3.3-4)
|
|
| trusty |
Does not exist
(trusty was not-affected [vulnerable code introduced in 4.3])
|
|
| upstream |
Released
(4.3.3-4)
|
|
| xenial |
Not vulnerable
(vulnerable code introduced in 4.3)
|
|
| zesty |
Ignored
(end of life)
|
|
|
Patches: upstream: https://github.com/hibernate/hibernate-validator/commit/0ed45f37c4680998167179e631113a2c9cb5d113 |
||
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 7.0 |
| Attack vector | Local |
| Attack complexity | High |
| Privileges required | Low |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | High |
| Availability impact | High |
| Vector | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |