GHSA-8cw6-5qvp-q3wj
MEDIUMExposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL
Blast Radius
org.apache.spark:spark-core_2.10☕org.apache.spark:spark-core_2.10☕org.apache.spark:spark-core_2.11☕org.apache.spark:spark-core_2.11☕org.apache.spark:spark-core_2.11Real-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
In Apache Spark 2.1.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, it's possible for a malicious user to construct a URL pointing to a Spark cluster's UI's job and stage info pages, and if a user can be tricked into accessing the URL, can be used to cause script to execute and expose information from the user's view of the Spark UI. While some browsers like recent versions of Chrome and Safari are able to block this type of attack, current versions of Firefox (and possibly others) do not.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.spark:spark-core_2.10 | ≥ 2.1.0&&< 2.1.3 | 2.1.3 |
| ☕Maven | org.apache.spark:spark-core_2.10 | ≥ 2.2.0&&< 2.2.2 | 2.2.2 |
| ☕Maven | org.apache.spark:spark-core_2.11 | ≥ 2.1.0&&< 2.1.3 | 2.1.3 |
| ☕Maven | org.apache.spark:spark-core_2.11 | ≥ 2.2.0&&< 2.2.2 | 2.2.2 |
| ☕Maven | org.apache.spark:spark-core_2.11 | ≥ 2.3.0&&< 2.3.1 | 2.3.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.spark:spark-core_2.10. 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.spark:spark-core_2.10 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8cw6-5qvp-q3wj 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-8cw6-5qvp-q3wj 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-8cw6-5qvp-q3wj. 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-8cw6-5qvp-q3wj in your dependencies?
O3 detects GHSA-8cw6-5qvp-q3wj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.