Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

github логотип

GHSA-h7qf-qmf3-85qg

Опубликовано: 25 июн. 2025
Источник: github
Github: Прошло ревью
CVSS3: 7.5

Описание

Allure Report allows Improper XXE Restriction via DocumentBuilderFactory

Summary

A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2. The plugin fails to securely configure the XML parser (DocumentBuilderFactory) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF).

Details

In \allure2-main\plugins\xunit-xml-plugin\src\main\java\io\qameta\allure\xunitxml\XunitXmlPlugin.java the application uses DocumentBuilderFactory without disabling DTDs or external entities. By generating a report with a malicious xml file within it, an attacker can perform XXE to leverage SSRF, or to read system files.

PoC

To recreate this vulnerability, you need to install allure for command-line (In my POC I used a Windows 11 Machine).

  1. Create a folder called allure, and within it, create a malicious XML file. I will attach my SSRF and file reading payloads, however, for the rest of the POC, I will focus on reading system files for better screenshots. ##SSRF (replace webhook link with your own) image

##Reading System Files image

  1. Put the malicious .xml file into the allure directory created previously
  2. Run the following command to run the report allure generate C:\path\to\directory\allure -o report --clean
  3. To view and confirm the executed payload, run allure open report
  4. When the report opens, confirm the payload executedby going to Categories > Product defects > <payload response> image

Impact

The explained XXE vulnerability can lead to Arbitrary File Disclosure and Server-Side Request Forgery. This exploitation can also be carried out silently, meaning it can be carried out without user interaction if the tool is automated within an application, and can go undetected with a carefully crafted payload. This could allow a malicious actor to view other source codes which may contain API or product keys, internal application URLs, or other secret items. This makes it an especially high risk when ran within a CI/CD platform.

Пакеты

Наименование

io.qameta.allure.plugins:xunit-xml-plugin

maven
Затронутые версииВерсия исправления

<= 2.34.0

2.34.1

Наименование

io.qameta.allure.plugins:junit-xml-plugin

maven
Затронутые версииВерсия исправления

<= 2.34.0

2.34.1

Наименование

io.qameta.allure.plugins:trx-plugin

maven
Затронутые версииВерсия исправления

<= 2.34.0

2.34.1

EPSS

Процентиль: 10%
0.00034
Низкий

7.5 High

CVSS3

Дефекты

CWE-611

Связанные уязвимости

CVSS3: 7.5
nvd
8 месяцев назад

Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. A critical XML External Entity (XXE) vulnerability exists in the xunit-xml-plugin used by Allure 2 prior to version 2.34.1. The plugin fails to securely configure the XML parser (`DocumentBuilderFactory`) and allows external entity expansion when processing test result .xml files. This allows attackers to read arbitrary files from the file system and potentially trigger server-side request forgery (SSRF). Version 2.34.1 contains a patch for the issue.

EPSS

Процентиль: 10%
0.00034
Низкий

7.5 High

CVSS3

Дефекты

CWE-611