Skip to content

XXE vulnerability in Jenkins Filesystem Trigger Plugin

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Oct 27, 2023

Package

maven org.jenkins-ci.plugins:fstrigger (Maven)

Affected versions

<= 0.40

Patched versions

0.41

Description

Jenkins Filesystem Trigger Plugin 0.40 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

This allows attackers with Job/Configure permission or otherwise able to control the contents of an XML file being polled for changes to have Jenkins parse a crafted XML document that uses external entities for extraction of secrets from the polling Jenkins controller or agent, server-side request forgery, or denial-of-service attacks.

Jenkins Filesystem Trigger Plugin 0.41 disables external entity resolution for its XML parser.

References

Published by the National Vulnerability Database May 25, 2021
Published to the GitHub Advisory Database May 24, 2022
Reviewed Dec 15, 2022
Last updated Oct 27, 2023

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
High

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:H

EPSS score

0.093%
(41st percentile)

Weaknesses

CVE ID

CVE-2021-21657

GHSA ID

GHSA-cphv-7cxw-5hcc

Source code

Credits

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