GitHub Advisoryadvisory · Maven

GHSA-chfm-68vv-pvw5 XMLUnit for Java has Insecure Defaults when Processing XSLT Stylesheets

LOW Published 2024-05-01 Modified 2024-05-01 Official page ↗
Aliases
CVE-2024-31573
Ecosystem
Maven
Packages
org.xmlunit:xmlunit-core
Severity
Low
Reviewed
2024-05-01

Affected packages

• Maven org.xmlunit:xmlunit-core: < 2.10.0 → fixed in 2.10.0

Description

Impact When performing XSLT transformations XMLUnit for Java did not disable XSLT extension functions by default. Depending on the XSLT processor being used this could allow arbitrary code to be executed when XMLUnit is used to transform data with a stylesheet who's source can not be trusted. If the stylesheet can be provided externally this may even lead to a remote code execution. Patches Users are advised to upgrade to XMLUnit for Java 2.10.0 where the default has been changed by means of https://github.com/xmlunit/xmlunit/commit/b81d48b71dfd2868bdfc30a3e17ff973f32bc15b Workarounds XMLUnit's main use-case is performing tests on code that generates or processes XML. Most users will not use it to perform arbitrary XSLT transformations. Users running XSLT transformations with untrusted stylesheets should explicitly use XMLUnit's APIs to pass in a pre-configured TraX `TransformerFactory` with extension functions disabled via features and attributes. The required `setFactory` or `setTransformerFactory` methods have been available since XMLUnit for Java 2.0.0. References Bug Report JAXP Security Guide

Related

Alias · CVE (1)

  • CVE-2024-31573 XMLUnit for Java before 2.10.0, in the default configuration, might allow code execution via an untrusted stylesheet (used for an XSLT… vulnerability

References