CVE-2018-8023GHSA-C8CC-P3J7-4C7F
Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT).
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.2, 1.5.2, 1.6.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache Mesos
versions prior to 1.4.2, 1.6.0
- org.apache.mesos:mesosMaven
fixed in 1.4.2
- org.apache.mesos:mesosMaven
From 1.5.0 · fixed in 1.5.2
- org.apache.mesos:mesosMaven
From 1.6.0 · fixed in 1.6.1