Skip to content

Missing permission checks in Jenkins Chef Sinatra Plugin allow XXE

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

Package

maven org.jenkins-ci.plugins:sinatra-chef-builder (Maven)

Affected versions

<= 1.20

Patched versions

None

Description

Jenkins Chef Sinatra Plugin 1.20 and earlier does not perform a permission check in a method implementing form validation.

This allows attackers with Overall/Read permission to have Jenkins send an HTTP request to an attacker-controlled URL and have it parse the response as XML.

As the plugin does not configure its XML parser to prevent XML external entity (XXE) attacks, attackers can have Jenkins parse a crafted XML response that uses external entities for extraction of secrets from the Jenkins controller or server-side request forgery.

Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.

References

Published by the National Vulnerability Database Feb 15, 2022
Published to the GitHub Advisory Database Feb 16, 2022
Reviewed Dec 1, 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-2022-25208

GHSA ID

GHSA-fq56-c7rj-j3j9

Source code

Credits

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