# CVE-2022-38663: Improper masking of credentials Jenkins in Git Plugin

> Attackers can view sensitive credentials in build logs because the Jenkins Git Plugin fails to mask them properly.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 23 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-jxmw-3gxf-fprh

## What is CVE-2022-38663?

CVE-2022-38663 is a medium-severity vulnerability in Jenkins Git Plugin, published on 23 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Git Plugin 4.11.4 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log provided by the Git Username and Password (`gitUsernamePassword`) credentials binding.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:git` | Maven | All versions | 4.11.5 |
| `org.jenkins-ci.plugins:git` | Maven | All versions | 4.11.5 |

Products: Jenkins Git.

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

Upgrade org.jenkins-ci.plugins:git to 4.11.5 or later.

## Is CVE-2022-38663 being exploited?

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

## Other vulnerabilities in Jenkins Git Plugin

- [CVE-2022-36882](https://insights.sbomify.com/CVE-2022-36882/): Lack of authentication mechanism in Jenkins Git Plugin webhook (high 8.8)
- [CVE-2022-36883](https://insights.sbomify.com/CVE-2022-36883/): Lack of authentication mechanism in Jenkins Git Plugin webhook (high 7.5)
- [CVE-2022-30947](https://insights.sbomify.com/CVE-2022-30947/): Path traversal in Jenkins Git Mercurial and Repo Plugins (high 7.5)
- [CVE-2017-1000092](https://insights.sbomify.com/CVE-2017-1000092/): Cross-Site Request Forgery in Jenkins Git Plugin (high 7.5)
- [CVE-2018-1000182](https://insights.sbomify.com/CVE-2018-1000182/): Server-Side Request Forgery in Jenkins Git Plugin (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38663 is a medium-severity vulnerability in Jenkins Git Plugin, published on 23 Aug 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-38663 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:git (Maven): affected all versions; fixed in 4.11.5
- org.jenkins-ci.plugins:git (Maven): affected all versions; fixed in 4.11.5

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-38663/ (Markdown: https://insights.sbomify.com/CVE-2022-38663/index.md)
```

## Sources

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

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