# CVE-2019-1010241: Jenkins Credentials Binding Plugin Stores Passwords in a Recoverable Format

> Authenticated users can recover stored credentials from the Jenkins Credentials Binding Plugin due to insecure storage formats.

- **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:** No
- **Published:** 19 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j7gw-mwfg-vqf4

## What is CVE-2019-1010241?

CVE-2019-1010241 is a medium-severity vulnerability in Jenkins, published on 19 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Credentials Binding Plugin Jenkins 1.17 is affected by: CWE-257: Storing Passwords in a Recoverable Format. The impact is: Authenticated users can recover credentials. The component is: config-variables.jelly line #30 (passwordVariable). The attack vector is: Attacker creates and executes a Jenkins job.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-257 (Storing Passwords in a Recoverable Format)

## Which versions are affected by CVE-2019-1010241?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | None |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | None |

Products: Jenkins Credentials Binding.

## How do I fix CVE-2019-1010241?

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

## Is CVE-2019-1010241 being exploited?

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

## Other vulnerabilities in Jenkins

- [CVE-2026-48922](https://insights.sbomify.com/CVE-2026-48922/): Jenkins Credentials Binding Plugin does not properly sanitize file names for file and zip file credentials (high 7.5)
- [CVE-2026-42520](https://insights.sbomify.com/CVE-2026-42520/): Jenkins Credentials Binding Plugin has a path traversal vulnerability (high 7.5)
- [CVE-2025-53650](https://insights.sbomify.com/CVE-2025-53650/): Jenkins Credentials Binding Plugin vulnerability can expose sensitive information in logger messages (high 7.3)
- [CVE-2020-2181](https://insights.sbomify.com/CVE-2020-2181/): Secrets are not masked by Jenkins Credentials Binding Plugin in builds without build steps (medium 6.5)
- [CVE-2022-20616](https://insights.sbomify.com/CVE-2022-20616/): Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010241 and fix it if it is affected.

What it is: CVE-2019-1010241 is a medium-severity vulnerability in Jenkins, published on 19 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1010241 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; no fix listed
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; 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-2019-1010241/ (Markdown: https://insights.sbomify.com/CVE-2019-1010241/index.md)
```

## Sources

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

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