# CVE-2018-8023: Moderate severity vulnerability that affects org.apache.mesos:mesos

> Timing attack in JWT validation allows attackers to reveal HMAC values, potentially bypassing authentication in Apache Mesos.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 21 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c8cc-p3j7-4c7f

## What is CVE-2018-8023?

CVE-2018-8023 is a medium-severity vulnerability in Apache Mesos, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

6 open source packages ship an affected version, including org.apache.mesos:mesos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.mesos:mesos` | Maven | All versions | 1.4.2 |
| `org.apache.mesos:mesos` | Maven | All versions | 1.4.2 |
| `org.apache.mesos:mesos` | Maven | From 1.5.0 | 1.5.2 |
| `org.apache.mesos:mesos` | Maven | From 1.5.0 | 1.5.2 |
| `org.apache.mesos:mesos` | Maven | From 1.6.0 | 1.6.1 |
| `org.apache.mesos:mesos` | Maven | From 1.6.0 | 1.6.1 |

Products: Apache Mesos.

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

Upgrade org.apache.mesos:mesos to a fixed version for your release line: 1.4.2, 1.5.2 or 1.6.1.

## Is CVE-2018-8023 being exploited?

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

## Other vulnerabilities in Apache Mesos

- [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-8023 and fix it if it is affected.

What it is: CVE-2018-8023 is a medium-severity vulnerability in Apache Mesos, published on 21 Sep 2018. 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-2018-8023 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.mesos:mesos (Maven): affected all versions; fixed in 1.4.2
- org.apache.mesos:mesos (Maven): affected all versions; fixed in 1.4.2
- org.apache.mesos:mesos (Maven): affected from 1.5.0; fixed in 1.5.2
- org.apache.mesos:mesos (Maven): affected from 1.5.0; fixed in 1.5.2
- org.apache.mesos:mesos (Maven): affected from 1.6.0; fixed in 1.6.1
- org.apache.mesos:mesos (Maven): affected from 1.6.0; fixed in 1.6.1

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

## Sources

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

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