# CVE-2018-1000421: Server-side request forgery vulnerability in Jenkins Mesos Plugin

> Attackers with read access can trigger SSRF to capture Jenkins credentials by connecting to malicious Mesos servers.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 9 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5q7j-8hpc-4848

## What is CVE-2018-1000421?

CVE-2018-1000421 is a medium-severity server-side request forgery vulnerability in n/a, published on 9 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper authorization vulnerability exists in Jenkins Mesos Plugin 0.17.1 and earlier in MesosCloud.java that allows attackers with Overall/Read access to initiate a test connection to an attacker-specified Mesos server with attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:mesos` | Maven | All versions | 0.18 |
| `org.jenkins-ci.plugins:mesos` | Maven | All versions | 0.18 |

Products: Apache Mesos.

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

Upgrade org.jenkins-ci.plugins:mesos to 0.18 or later.

## Is CVE-2018-1000421 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-5736](https://insights.sbomify.com/CVE-2019-5736/): Privilege escalation in n/a (high 8.6)
- [CVE-2019-0204](https://insights.sbomify.com/CVE-2019-0204/): Docker image code execution with Apache Mesos (high 7.8)
- [CVE-2018-11793](https://insights.sbomify.com/CVE-2018-11793/): Stack Overflow in Apache Mesos (high 7.5)
- [CVE-2018-1330](https://insights.sbomify.com/CVE-2018-1330/): Crash when decoding malformed HTTP requests or malformed JSON payload (high 7.5)
- [CVE-2017-7687](https://insights.sbomify.com/CVE-2017-7687/): Denial of service in Apache Mesos (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000421 is a medium-severity server-side request forgery vulnerability in n/a, published on 9 Jan 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-2018-1000421 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:mesos (Maven): affected all versions; fixed in 0.18
- org.jenkins-ci.plugins:mesos (Maven): affected all versions; fixed in 0.18

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

## Sources

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

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