# CVE-2017-1000403: Arbitrary code execution vulnerability in Jenkins Speaks! Plugin

> Users with Job/Configure permission can execute arbitrary Groovy code, escalating privileges to run scripts in the Jenkins JVM.

- **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:** No
- **Published:** 26 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5532-prrf-rf5x

## What is CVE-2017-1000403?

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

### Official description

Jenkins Speaks! Plugin, all current versions, allows users with Job/Configure permission to run arbitrary Groovy code inside the Jenkins JVM, effectively elevating privileges to Overall/Run Scripts.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-1000403?

2 open source packages ship an affected version, including org.jvnet.hudson.plugins:speaks. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jvnet.hudson.plugins:speaks` | Maven | All versions to 0.1.1 | None |
| `org.jvnet.hudson.plugins:speaks` | Maven | All versions to 0.1.1 | None |

Products: Jenkins Speaks\!.

## How do I fix CVE-2017-1000403?

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

## Is CVE-2017-1000403 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000403 and fix it if it is affected.

What it is: CVE-2017-1000403 is a high-severity code injection vulnerability in n/a, published on 26 Jan 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-2017-1000403 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jvnet.hudson.plugins:speaks (Maven): affected all versions up to 0.1.1; no fix listed
- org.jvnet.hudson.plugins:speaks (Maven): affected all versions up to 0.1.1; 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-2017-1000403/ (Markdown: https://insights.sbomify.com/CVE-2017-1000403/index.md)
```

## Sources

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

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