# CVE-2018-1000610: Jenkins Configuration as Code Plugin has Insufficiently Protected Credentials

> Attackers with log file access can obtain passwords configured via the Jenkins Configuration as Code Plugin.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 26 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8486-h39x-cx2f

## What is CVE-2018-1000610?

CVE-2018-1000610 is a high-severity vulnerability in n/a, published on 26 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in DataBoundConfigurator.java, Attribute.java, BaseConfigurator.java, ExtensionConfigurator.java that allows attackers with access to Jenkins log files to obtain the passwords configured using Configuration as Code Plugin.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2018-1000610?

2 open source packages ship an affected version, including io.jenkins:configuration-as-code. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins:configuration-as-code` | Maven | All versions | 0.8-alpha |
| `io.jenkins:configuration-as-code` | Maven | All versions | 0.8-alpha |

Products: Jenkins Configuration as Code.

## How do I fix CVE-2018-1000610?

Upgrade io.jenkins:configuration-as-code to 0.8-alpha or later.

## Is CVE-2018-1000610 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1000609](https://insights.sbomify.com/CVE-2018-1000609/): Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information (medium 6.5)
- [CVE-2019-10367](https://insights.sbomify.com/CVE-2019-10367/): Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin (medium 5.5)
- [CVE-2019-10345](https://insights.sbomify.com/CVE-2019-10345/): Plaintext Storage of a Password in Jenkins Configuration as Code Plugin (medium 5.5)
- [CVE-2019-10362](https://insights.sbomify.com/CVE-2019-10362/): Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin (medium 5.4)
- [CVE-2022-23106](https://insights.sbomify.com/CVE-2022-23106/): Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000610 and fix it if it is affected.

What it is: CVE-2018-1000610 is a high-severity vulnerability in n/a, published on 26 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000610 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins:configuration-as-code (Maven): affected all versions; fixed in 0.8-alpha
- io.jenkins:configuration-as-code (Maven): affected all versions; fixed in 0.8-alpha

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

## Sources

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

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