dbcve.org
SparkApplication · Apache

CVE-2022-31777

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored XSS vulnerability in Apache Spark's web UI allows remote attackers to inject malicious JavaScript into log entries. When users view these logs in the UI, the unsanitized payload executes in their browsers, enabling session hijacking or other client-side attacks.

MitigationUpgrade to Apache Spark 3.2.2 or 3.3.1 (or later) which contains proper input sanitization for log output. If immediate upgrade is not feasible, consider disabling the Spark UI or restricting UI access via network controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SparkApplication
Affected:< 3.2.2= 3.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Spark version
    Run 'spark-submit --version' or 'spark-shell --version' to obtain the exact version number. Alternatively, check the SPARK_HOME environment variable or examine the spark-core JAR file name.
    Affected if The version is lower than 3.2.2, or the version is exactly 3.3.0
  2. Verify Spark UI is enabled
    Check the Spark configuration for the property 'spark.ui.enabled'. This can be found in spark-defaults.conf, or retrieved via the Spark history server API at /api/v1/applications/{app_id}/configuration.
    Affected if spark.ui.enabled is set to true (this is the default; the vulnerability only applies when the UI is active)
  3. Confirm network exposure of the Spark UI
    Inspect the 'spark.ui.bindAddress' and 'spark.master.rest.enabled' configuration values. Check if the UI listener is bound to 0.0.0.0 or an external interface rather than localhost only.
    Affected if The UI is accessible over the network (bound to non-localhost interface) - this makes the stored XSS exploitable by remote attackers

You are affected if your Spark version is below 3.2.2 or exactly 3.3.0 AND the Spark web UI is enabled and network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.2 or later
Fixed in 3.2.2
Interim mitigation

Upgrade to Apache Spark 3.2.2 or 3.3.1 (or later) which contains proper input sanitization for log output. If immediate upgrade is not feasible, consider disabling the Spark UI or restricting UI access via network controls.

Recommended fix High confidence

Spark 3.2.2 (for versions < 3.2.2) or Spark 3.3.1+ (for version 3.3.0)

  1. 1. Identify current Spark version by running: spark-submit --version or checking Spark UI
  2. 2. If running version < 3.2.2: Plan upgrade to Spark 3.2.2 or later
  3. 3. If running version = 3.3.0: Plan upgrade to Spark 3.3.1 or later
  4. 4. Review Apache Spark release notes for the target version to understand changes
  5. 5. Back up all Spark configuration files (spark-defaults.conf, spark-env.sh, etc.)
  6. 6. Test upgrade in a non-production environment first
  7. 7. Stop all running Spark applications and services
  8. 8. Upgrade Spark installation to the target version
Caveat Minor version upgrades may introduce behavioral changes; review release notes for breaking changes between your current version and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spark Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data