CVE-2022-31777 — spark-core_2.9.3
MEDIUMCVE-2022-31777 is a medium-severity (CVSS 5.4) CWE-74 vulnerability in org.apache.spark:spark-core_2.9.3. A fix is available for org.apache.spark:spark-core_2.9.3 — see the affected versions and patch details below.
Apache Spark XSS vulnerability in log viewer UI Javascript
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31777.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-31777 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.spark:spark-core_2.9.3☕org.apache.spark:spark-core_2.13☕org.apache.spark:spark-core_2.13☕org.apache.spark:spark-core_2.12☕org.apache.spark:spark-core_2.12☕org.apache.spark:spark-core_2.11☕org.apache.spark:spark-core_2.10🐍pyspark+1 moreReal-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
A stored cross-site scripting (XSS) vulnerability in Apache Spark 3.2.1 and earlier, and 3.3.0, allows remote attackers to execute arbitrary JavaScript in the web browser of a user, by including a malicious payload into the logs which would be returned in logs rendered in the UI.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.spark:spark-core_2.9.3 | all versions | No fix |
| ☕Maven | org.apache.spark:spark-core_2.13 | all versions | 3.2.2org.apache.spark:spark-core_2.13:3.2.2 |
| ☕Maven | org.apache.spark:spark-core_2.13 | ≥ 3.3.0&&< 3.3.1 | 3.3.1org.apache.spark:spark-core_2.13:3.3.1 |
| ☕Maven | org.apache.spark:spark-core_2.12 | all versions | 3.2.2org.apache.spark:spark-core_2.12:3.2.2 |
| ☕Maven | org.apache.spark:spark-core_2.12 | ≥ 3.3.0&&< 3.3.1 | 3.3.1org.apache.spark:spark-core_2.12:3.3.1 |
| ☕Maven | org.apache.spark:spark-core_2.11 | all versions | No fix |
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.9.3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.apache.spark:spark-core_2.9.3 has shipped for CVE-2022-31777 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-31777 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-31777. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHINT Camel-Springboot 3.20.1 | apache-spark | RHSA-2023:2100 |
Frequently Asked Questions
Is CVE-2022-31777 in your dependencies?
O3 Security finds CVE-2022-31777 across Maven, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.