veraPDF-validatio: Use of Default `DocumentBuilderFactory` leads to XXE When Processing Untrusted PDFs
veraPDF-validation
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.verapdf:validation-model Maven |
|
|
| org.verapdf:validation-model-jakarta Maven |
|
veraPDF-validation
| Product | Affected | Fixed in |
|---|---|---|
| org.verapdf:validation-model Maven |
|
|
| org.verapdf:validation-model-jakarta Maven |
|
|
veraPDF validation model is an implementation of the veraPDF validation model. From 1.25.73 until 1.30.2 and 1.31.71, veraPDF-validation contains an XML External Entity vulnerability in PDFAValidator.validate(...) and GFPDAcroForm.getdynamicRender(), where default DocumentBuilderFactory parsing of rich-text annotation or form-field values and XFA configurations in untrusted PDFs can allow local file disclosure and outbound network requests. This issue is fixed in versions 1.30.2 and 1.31.71.
From the CVE record · GitHub_M
veraPDF-validation uses XML parsing that is vulnerable to external entities in rich-text annotation or form-field values and XFA configurations. When it processes an untrusted PDF, an attacker can cause local file disclosure or outbound network requests.
Engineers using Maven org.verapdf:validation-model or org.verapdf:validation-model-jakarta versions >=1.17.35 <1.30.2 or >=1.31.1 <1.31.71 should check their dependencies.