# CVE-2022-25181: Jenkins Pipeline: Deprecated Groovy Libraries Plugin Protection Mechanism Failure

> Attackers with configure permissions can execute arbitrary code on the Jenkins controller via crafted SCM contents if a global library exists.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7w2w-fwpf-9m4h

## What is CVE-2022-25181?

CVE-2022-25181 is a high-severity code injection vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A sandbox bypass vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin 552.vd9cc05b8a2e1 and earlier allows attackers with Item/Configure permission to execute arbitrary code in the context of the Jenkins controller JVM through crafted SCM contents, if a global Pipeline library already exists.

## Which versions are affected by CVE-2022-25181?

2 open source packages ship an affected version, including org.jenkins-ci.plugins.workflow:workflow-cps-global-lib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins.workflow:workflow-cps-global-lib` | Maven | All versions | 561.va_ce0de3c2d69 |
| `org.jenkins-ci.plugins.workflow:workflow-cps-global-lib` | Maven | All versions | 561.va_ce0de3c2d69 |

Products: Jenkins Pipeline\.

## How do I fix CVE-2022-25181?

Upgrade org.jenkins-ci.plugins.workflow:workflow-cps-global-lib to 561.va_ce0de3c2d69 or later.

## Is CVE-2022-25181 being exploited?

There is no known exploitation of CVE-2022-25181 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Pipeline: Shared Groovy Libraries Plugin

- [CVE-2019-1003030](https://insights.sbomify.com/CVE-2019-1003030/): Jenkins Matrix Project Plugin Remote Code Execution (critical 9.9, exploited in the wild)
- [CVE-2022-43402](https://insights.sbomify.com/CVE-2022-43402/): Jenkins Pipeline: Groovy Plugin allows sandbox protection bypass and arbitrary code execution (critical 9.9)
- [CVE-2019-1003041](https://insights.sbomify.com/CVE-2019-1003041/): Sandbox bypass vulnerability in Jenkins Pipeline: Groovy Plugin (critical 9.8)
- [CVE-2022-43407](https://insights.sbomify.com/CVE-2022-43407/): CSRF protection for any URL can be bypassed in Jenkins Pipeline: Input Step Plugin (high 8.8)
- [CVE-2022-25173](https://insights.sbomify.com/CVE-2022-25173/): Improper Neutralization of Special Elements used in an OS Command in Jenkins Pipeline: Groovy Plugin (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25181 and fix it if it is affected.

What it is: CVE-2022-25181 is a high-severity code injection vulnerability in Jenkins Pipeline: Shared Groovy Libraries Plugin, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25181 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven): affected all versions; fixed in 561.va_ce0de3c2d69
- org.jenkins-ci.plugins.workflow:workflow-cps-global-lib (Maven): affected all versions; fixed in 561.va_ce0de3c2d69

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25181/ (Markdown: https://insights.sbomify.com/CVE-2022-25181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25181
- OSV: https://osv.dev/vulnerability/CVE-2022-25181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25181/
Summaries are generated and may contain mistakes; the official description above is the record.