GHSA-c8cc-p3j7-4c7f
MEDIUMGHSA-c8cc-p3j7-4c7f is a medium-severity (CVSS 5.9) Information Exposure vulnerability in org.apache.mesos:mesos. O3 Security confirms whether GHSA-c8cc-p3j7-4c7f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Moderate severity vulnerability that affects org.apache.mesos:mesos
Blast Radius
org.apache.mesos:mesos☕org.apache.mesos:mesos☕org.apache.mesos:mesosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.mesos:mesos | all versions | 1.4.2 |
| ☕Maven | org.apache.mesos:mesos | ≥ 1.5.0&&< 1.5.2 | 1.5.2 |
| ☕Maven | org.apache.mesos:mesos | ≥ 1.6.0&&< 1.6.1 | 1.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mesos:mesos. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.mesos:mesos to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c8cc-p3j7-4c7f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c8cc-p3j7-4c7f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-c8cc-p3j7-4c7f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-c8cc-p3j7-4c7f in your dependencies?
O3 detects GHSA-c8cc-p3j7-4c7f across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.