Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-7gj7-224w-vpr3

HIGH

GHSA-7gj7-224w-vpr3 is a high-severity (CVSS 7.5) CWE-77 vulnerability in de.codecentric:spring-boot-admin-server. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-7gj7-224w-vpr3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring-boot-admin sandbox bypass via crafted HTML

Also known asCVE-2023-38286
Published
Jul 14, 2023
Updated
Jun 12, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known

Blast Radius

2 pkgs affected
de.codecentric:spring-boot-admin-serverde.codecentric:spring-boot-admin-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavende.codecentric:spring-boot-admin-server3.0.0&&< 3.1.23.1.2
Mavende.codecentric:spring-boot-admin-serverall versions2.7.16
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.codecentric:spring-boot-admin-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update de.codecentric:spring-boot-admin-server to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7gj7-224w-vpr3 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7gj7-224w-vpr3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7gj7-224w-vpr3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.s
O3 Security · Impact-Aware SCA

Is GHSA-7gj7-224w-vpr3 in your dependencies?

O3 detects GHSA-7gj7-224w-vpr3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.