GitHub Advisoryadvisory · Maven
GHSA-4cx5-89vm-833x veraPDF CLI has potential XXE (XML External Entity Injection) vulnerability
LOW
Official page ↗
- Aliases
- CVE-2024-52800
- Ecosystem
- Maven
- Packages
- org.verapdf:core, org.verapdf:core-jakarta, org.verapdf:core-arlington, org.verapdf:verapdf-library, org.verapdf:verapdf-library-jakarta, org.verapdf:verapdf-library-arlington, org.verapdf:library, org.verapdf:library-jakarta, org.verapdf:library-arlington
- Severity
- Low
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- Weaknesses
- CWE-611
- Reviewed
- 2024-12-02
Affected packages
• Maven org.verapdf:core: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:core-jakarta: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:core-arlington: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:verapdf-library: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:verapdf-library-jakarta: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:verapdf-library-arlington: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:library: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:library-jakarta: < 1.26.2 → fixed in 1.26.2
• Maven org.verapdf:library-arlington: < 1.26.2 → fixed in 1.26.2
Description
Impact
Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability.
Patches
We are currently working on a patch that will be released when ready.
Workarounds
This doesn't affect the standard validation and policy checks functionality, veraPDF's common use cases. Most veraPDF users don't insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust.
References
Original issue: #1488
Related
Alias · CVE (1)
- CVE-2024-52800 veraPDF is an open source PDF/A validation library. vulnerability
Weakness · CWE (1)
- CWE-611 Improper Restriction of XML External Entity Reference weakness