# CVE-2019-16568: Jenkins SCTMExecutor Plugin stores credentials in plain text

> The Jenkins SCTMExecutor Plugin exposes service credentials in plain text within global and job configurations, allowing attackers to read sensitive authentication data.

- **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:** No
- **Published:** 17 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rxph-cq38-gm3g

## What is CVE-2019-16568?

CVE-2019-16568 is a medium-severity vulnerability in Jenkins SCTMExecutor Plugin, published on 17 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins SCTMExecutor Plugin 2.2 and earlier transmits previously configured service credentials in plain text as part of the global configuration, as well as individual jobs' configurations.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

2 open source packages ship an affected version, including hudson.plugins.sctmexecutor:SCTMExecutor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hudson.plugins.sctmexecutor:SCTMExecutor` | Maven | All versions to 2.2 | None |
| `hudson.plugins.sctmexecutor:SCTMExecutor` | Maven | All versions to 2.2 | None |

Products: Jenkins Sctmexecutor.

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

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

## Is CVE-2019-16568 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16568 is a medium-severity vulnerability in Jenkins SCTMExecutor Plugin, published on 17 Dec 2019. 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-2019-16568 in the wild and no public exploit code.

Affected packages and fixed versions:
- hudson.plugins.sctmexecutor:SCTMExecutor (Maven): affected all versions up to 2.2; no fix listed
- hudson.plugins.sctmexecutor:SCTMExecutor (Maven): affected all versions up to 2.2; 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-16568/ (Markdown: https://insights.sbomify.com/CVE-2019-16568/index.md)
```

## Sources

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

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