Skip to content

Privilege Escalation in Hibernate Validator

High severity GitHub Reviewed Published Jun 15, 2020 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven org.hibernate:hibernate-validator (Maven)

Affected versions

>= 5.2.0, <= 5.2.4.Final
>= 5.3.0, <= 5.3.5.Final
>= 5.4.0, <= 5.4.1.Final

Patched versions

5.2.5.Final
5.3.6.Final
5.4.2.Final

Description

In Hibernate Validator 5.2.x before 5.2.5.Final, 5.3.x before 5.3.6.Final, and 5.4.x before 5.4.2.Final, 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().

References

Published by the National Vulnerability Database Jan 10, 2018
Reviewed Jun 11, 2020
Published to the GitHub Advisory Database Jun 15, 2020
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.064%
(29th percentile)

Weaknesses

CVE ID

CVE-2017-7536

GHSA ID

GHSA-xxgp-pcfc-3vgc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.