Skip to content

Spring-boot-admin sandbox bypass via crafted HTML

High severity GitHub Reviewed Published Jul 14, 2023 to the GitHub Advisory Database • Updated Jun 12, 2024

Package

maven de.codecentric:spring-boot-admin-server (Maven)

Affected versions

>= 3.0.0, < 3.1.2
< 2.7.16

Patched versions

3.1.2
2.7.16

Description

Thymeleaf through 3.1.1.RELEASE as used in spring-boot-admin (aka Spring Boot Admin) through 3.1.1 allows for a sandbox bypass via crafted HTML. This may be relevant for SSTI (Server Side Template Injection) and code execution in spring-boot-admin if MailNotifier is enabled and there is write access to environment variables via the UI.

Spring Boot Admin 3.1.2 and 2.7.16 contain mitigations for the issue. This bypass is achived via a library called Thymeleaf which has added counter measures for this sort of bypass in version 3.1.2.RELEASE which has explicity forbidden static access to org.springframework.util in expressions. Thymeleaf itself should not be considered vulnerable.

References

Published by the National Vulnerability Database Jul 14, 2023
Published to the GitHub Advisory Database Jul 14, 2023
Reviewed Jul 14, 2023
Last updated Jun 12, 2024

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
Network
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:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.086%
(37th percentile)

Weaknesses

CVE ID

CVE-2023-38286

GHSA ID

GHSA-7gj7-224w-vpr3

Source code

Credits

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