Improper restriction of the scope of accessible objects in Thymeleaf expressions
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.1.4.RELEASE
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Thymeleaf is a server-side Java template engine for web and standalone environments. Versions 3.1.3.RELEASE and prior contain a security bypass vulnerability in the expression execution mechanisms. Although the library provides mechanisms to prevent expression injection, it fails to properly restrict the scope of accessible objects, allowing specific potentially sensitive objects to be reached from within a template. If an application developer passes unvalidated user input directly to the template engine, an unauthenticated remote attacker can bypass the library's protections to achieve Server-Side Template Injection (SSTI). This issue has ben fixed in version 3.1.4.RELEASE.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- thymeleaf thymeleaf
fixed in 3.1.4.RELEASE
- thymeleaf org.thymeleaf:thymeleaf-spring5
fixed in 3.1.4.RELEASE
- thymeleaf org.thymeleaf:thymeleaf-spring6
fixed in 3.1.4.RELEASE
- org.thymeleaf:thymeleafMaven
fixed in 3.1.4.RELEASE
- org.thymeleaf:thymeleaf-spring5Maven
fixed in 3.1.4.RELEASE
- org.thymeleaf:thymeleaf-spring6Maven
fixed in 3.1.4.RELEASE