# CVE-2019-10380: Jenkins Simple Travis Pipeline Runner Plugin script sandbox bypass vulnerability

> Attackers with script execution privileges can bypass security restrictions to run arbitrary code via unsafe whitelist configurations in the Jenkins Simple Travis Pipeline Runner Plugin.

- **Severity:** High 8.8 (`CVSS:3.1/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:** No
- **Published:** 7 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x7p9-vx6v-wv84

## What is CVE-2019-10380?

CVE-2019-10380 is a high-severity code injection vulnerability in Jenkins Simple Travis Pipeline Runner Plugin, published on 7 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Simple Travis Pipeline Runner Plugin 1.0 and earlier specifies unsafe values in its custom Script Security whitelist, allowing attackers able to execute Script Security protected scripts to execute arbitrary code.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:simple-travis-runner` | Maven | All versions to 1.0 | None |
| `org.jenkins-ci.plugins:simple-travis-runner` | Maven | All versions to 1.0 | None |

Products: Jenkins Simple Travis Pipeline Runner.

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

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

## Is CVE-2019-10380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10380 is a high-severity code injection vulnerability in Jenkins Simple Travis Pipeline Runner Plugin, published on 7 Aug 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-10380 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:simple-travis-runner (Maven): affected all versions up to 1.0; no fix listed
- org.jenkins-ci.plugins:simple-travis-runner (Maven): affected all versions up to 1.0; 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-10380/ (Markdown: https://insights.sbomify.com/CVE-2019-10380/index.md)
```

## Sources

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

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