CVE-2018-8023

mesos: Exposure of HMAC value via timing vulnerability in JWT validation

Published Sep 21, 2018 CVSS 3.0 · 5.9 Medium EPSS 3.1% KEV · Not listed
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2018-0571 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.
Github GHSA Github GHSA GHSA-c8cc-p3j7-4c7f Moderate severity vulnerability that affects org.apache.mesos:mesos
History

No history.

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-385

    Covert Timing Channel

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 16, 2024, 4:58 PM
Reserved
Mar 9, 2018, 12:00 AM
Status
Modified
Published
Sep 21, 2018, 1:29 PM
Modified
Jun 17, 2026, 2:04 AM
Severity
Moderate
Public date
Sep 21, 2018, 12:00 AM