veraPDF Validation XXE via XFA
- 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 1.30.2, 1.31.71
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
veraPDF validation provides PDF/A and PDF/UA validation, feature reporting, and metadata repair. From 1.17.35 until 1.30.2 and 1.31.71, veraPDF-validation contains an XML External Entity (XXE) vulnerability in validation-model/src/main/java/org/verapdf/gf/model/impl/pd/GFPDAcroForm.java in the getdynamicRender() method, where a crafted PDF containing a malicious XFA stream can cause external entity expansion during PDF/UA-1 validation and allow local file disclosure or outbound server-side requests. This issue is fixed in versions 1.30.2 and 1.31.71.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- veraPDF veraPDF-validation
From 1.17.35 · fixed in 1.30.2; From 1.31.1 · fixed in 1.31.71
- org.verapdf:validation-modelMaven
From 1.17.35 · fixed in 1.30.2
- org.verapdf:validation-modelMaven
From 1.31.1 · fixed in 1.31.71
- org.verapdf:validation-model-jakartaMaven
From 1.17.35 · fixed in 1.30.2
- org.verapdf:validation-model-jakartaMaven
From 1.31.1 · fixed in 1.31.71