# CVE-2023-41934: Improper masking of credentials in Jenkins Pipeline Maven Integration Plugin

> Attackers can view unmasked credential usernames in build logs when specific settings are enabled, exposing sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-9v8g-f9mq-739g

## What is CVE-2023-41934?

CVE-2023-41934 is a medium-severity vulnerability in Jenkins Pipeline Maven Integration Plugin, published on 6 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Pipeline Maven Integration Plugin 1330.v18e473854496 and earlier does not properly mask (i.e., replace with asterisks) usernames of credentials specified in custom Maven settings in Pipeline build logs if "Treat username as secret" is checked.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-41934?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 1331.v003efa_fd6e81 |
| `org.jenkins-ci.plugins:pipeline-maven` | Maven | All versions | 1331.v003efa_fd6e81 |

Products: Jenkins Pipeline Maven Integration.

## How do I fix CVE-2023-41934?

Upgrade org.jenkins-ci.plugins:pipeline-maven to 1331.v003efa_fd6e81 or later.

## Is CVE-2023-41934 being exploited?

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

## Other vulnerabilities in Jenkins Pipeline Maven Integration Plugin

- [CVE-2019-10327](https://insights.sbomify.com/CVE-2019-10327/): XML External Entity processing vulnerability in Pipeline Maven Integration Jenkins Plugin (high 8.1)
- [CVE-2020-2233](https://insights.sbomify.com/CVE-2020-2233/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allows enumerating credentials IDs (medium 6.5)
- [CVE-2020-2234](https://insights.sbomify.com/CVE-2020-2234/): Missing permission check in Jenkins Pipeline Maven Integration Plugin allow capturing credentials (medium 6.5)
- [CVE-2020-2235](https://insights.sbomify.com/CVE-2020-2235/): CSRF vulnerability in Jenkins Pipeline Maven Integration Plugin allow capturing credentials (medium 6.5)
- [CVE-2020-2256](https://insights.sbomify.com/CVE-2020-2256/): Stored XSS vulnerability in Pipeline Maven Integration Plugin via unescaped display name (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41934 and fix it if it is affected.

What it is: CVE-2023-41934 is a medium-severity vulnerability in Jenkins Pipeline Maven Integration Plugin, published on 6 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41934 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 1331.v003efa_fd6e81
- org.jenkins-ci.plugins:pipeline-maven (Maven): affected all versions; fixed in 1331.v003efa_fd6e81

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

## Sources

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

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