# CVE-2023-41941: Missing permission check in Jenkins AWS CodeCommit Trigger Plugin allows enumerating credentials IDs

> Attackers with read permissions can enumerate AWS credential IDs due to missing permission checks in the Jenkins AWS CodeCommit Trigger Plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** No
- **Published:** 6 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-pfg6-cj3j-rpv4

## What is CVE-2023-41941?

CVE-2023-41941 is a medium-severity missing authorization vulnerability in Jenkins AWS CodeCommit Trigger Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins AWS CodeCommit Trigger Plugin 3.0.12 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of AWS credentials stored in Jenkins.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:aws-codecommit-trigger` | Maven | All versions to 3.0.12 | None |
| `org.jenkins-ci.plugins:aws-codecommit-trigger` | Maven | All versions to 3.0.12 | None |

Products: Jenkins Aws Codecommit Trigger.

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

No fix has been published for CVE-2023-41941 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-41941 being exploited?

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

## Other vulnerabilities in Jenkins AWS CodeCommit Trigger Plugin

- [CVE-2023-41943](https://insights.sbomify.com/CVE-2023-41943/): Missing permission check in Jenkins AWS CodeCommit Trigger Plugin (medium 6.5)
- [CVE-2023-35147](https://insights.sbomify.com/CVE-2023-35147/): Arbitrary file read vulnerability in Jenkins AWS CodeCommit Trigger Plugin (medium 6.5)
- [CVE-2023-41944](https://insights.sbomify.com/CVE-2023-41944/): HTML injection vulnerability in Jenkins AWS CodeCommit Trigger Plugin (medium 6.1)
- [CVE-2023-41942](https://insights.sbomify.com/CVE-2023-41942/): CSRF vulnerability in Jenkins AWS CodeCommit Trigger Plugin (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41941 is a medium-severity missing authorization vulnerability in Jenkins AWS CodeCommit Trigger Plugin, published on 6 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41941 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:aws-codecommit-trigger (Maven): affected all versions up to 3.0.12; no fix listed
- org.jenkins-ci.plugins:aws-codecommit-trigger (Maven): affected all versions up to 3.0.12; no fix listed

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

## Sources

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

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