# CVE-2019-10362: Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin

> Attackers with system configuration permissions can read environment variables due to improper escaping during configuration export.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** Yes
- **Published:** 31 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5r6p-p9r6-r326

## What is CVE-2019-10362?

CVE-2019-10362 is a medium-severity vulnerability in Jenkins Configuration as Code Plugin, published on 31 Jul 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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

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 | 1.25 |
| `io.jenkins:configuration-as-code` | Maven | All versions | 1.25 |

Products: Jenkins Configuration as Code.

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

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

## Is CVE-2019-10362 being exploited?

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

## Other vulnerabilities in Jenkins Configuration as Code Plugin

- [CVE-2018-1000610](https://insights.sbomify.com/CVE-2018-1000610/): Jenkins Configuration as Code Plugin has Insufficiently Protected Credentials (high 8.8)
- [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-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-2019-10362 and fix it if it is affected.

What it is: CVE-2019-10362 is a medium-severity vulnerability in Jenkins Configuration as Code Plugin, published on 31 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-10362 in the wild and no public exploit code.

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

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

## Sources

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

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