compliance-trestle is a tooling platform for managing compliance as code. Prior to versions 3.12.2 and 4.0.3, the compliance-trestle library's profile import mechanism resolves `trestle://` URIs and relative file paths by joining them with `trestle_root` and calling `.resolve()`, but performs no boundary check to ensure the resolved path stays within the trestle workspace. An attacker can craft a malicious OSCAL profile YAML with `imports[].href` containing path traversal sequences to read arbitrary files from the server filesystem.
Versions 3.12.3 and 4.0.3 patch the issue.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
None
No privileges needed
User Interaction
Active
User action required
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 4
https://github.com/oscal-compass/compliance-trestle/commit/5c65c5926fe7ca908b9c…
security-advisories@github.com
https://github.com/oscal-compass/compliance-trestle/commit/d00a0c2f702c24f70160…
security-advisories@github.com
https://github.com/oscal-compass/compliance-trestle/security/advisories/GHSA-mj…
security-advisories@github.com
https://github.com/pypa/advisory-database/tree/main/vulns/compliance-trestle/PY…
security-advisories@github.com