Skip to content

veraPDF has potential XSLT injection vulnerability when using policy files

High severity GitHub Reviewed Published Mar 28, 2024 in veraPDF/veraPDF-library • Updated May 20, 2024

Package

maven org.verapdf:core (Maven)

Affected versions

< 1.24.2

Patched versions

1.24.2
maven org.verapdf:core-arlington (Maven)
< 1.25.127
1.25.127
maven org.verapdf:core-jakarta (Maven)
< 1.24.2
1.24.2
maven org.verapdf:library (Maven)
< 1.24.2
1.24.2
maven org.verapdf:library-arlington (Maven)
< 1.25.127
1.25.127
maven org.verapdf:library-jakarta (Maven)
< 1.24.2
1.24.2

Description

Impact

Executing policy checks using custom schematron files invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability.

Patches

This has been patched and users should upgrade to veraPDF v1.24.2

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: veraPDF/veraPDF-library#1415

References

@carlwilson carlwilson published to veraPDF/veraPDF-library Mar 28, 2024
Published by the National Vulnerability Database Mar 28, 2024
Published to the GitHub Advisory Database May 20, 2024
Reviewed May 20, 2024
Last updated May 20, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2024-28109

GHSA ID

GHSA-qxqf-2mfx-x8jw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.