CyberRota Analysis
AI-GeneratedVersions of Compliance-trestle prior to 3.12.4 and between 4.0.0 and 4.0.3 are vulnerable to server-side template injection, allowing attackers to execute arbitrary operating system commands through crafted Markdown or YAML content. This vulnerability poses a significant risk to any organization utilizing Trestle for OSCAL compliance management, particularly those managing sensitive data or operating in regulated environments. Users should prioritize upgrading to versions 3.12.4 or 4.1.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Compliance-trestle (Trestle) is a Python SDK and command-line tool for managing OSCAL compliance documents. In versions before 3.12.4 and versions 4.0.0 through 4.0.3, Trestle is vulnerable to server-side template injection that can lead to remote code execution. This occurs because the MDCleanInclude and MDSectionInclude Jinja2 tags re-parse untrusted Markdown content as template source code using a non-sandboxed jinja2.Environment. An attacker who controls content that Trestle renders, such as a crafted workspace Markdown file, a third-party SSP document, or a YAML lookup-table value, can inject a Jinja2 expression that traverses Python object internals to execute arbitrary operating system commands in the context of the Trestle process. This issue is fixed in versions 3.12.4 and 4.1.0.