Skip to content

Jenkins Pipeline: Deprecated Groovy Libraries Plugin Protection Mechanism Failure

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

Package

maven org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven)

Affected versions

<= 552.vd9cc05b8a2e1

Patched versions

561.va_ce0de3c2d69

Description

Jenkins Pipeline: Deprecated Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier uses the names of Pipeline libraries to create directories without canonicalization or sanitization.

This allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM using specially crafted library names if a global Pipeline library is already configured.

Pipeline: Deprecated Groovy Libraries Plugin 561.va_ce0de3c2d69 sanitizes the names of Pipeline libraries when creating library directories.

References

Published by the National Vulnerability Database Feb 15, 2022
Published to the GitHub Advisory Database Feb 16, 2022
Reviewed Jun 20, 2022
Last updated Dec 22, 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.104%
(44th percentile)

Weaknesses

CVE ID

CVE-2022-25182

GHSA ID

GHSA-7rcw-fwfh-2h2g

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.