CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighResearch in progress

CVE-2022-33891 remediation guide

Apache Spark

The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is curren...

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductApache Spark
Affected versions3.0.3 and earlier, 3.1.1 to 3.1.2, 3.2.0 to 3.2.1, <= 3.0.3, >= 3.1.1 <= 3.1.2, >= 3.2.0 <= 3.2.1
Fixed versionsNo verified fixed-version field is available yet
Priority basisImmediate · CVSS 8.8 · EPSS 93.1%
01

Identify the affected asset

Confirm whether Apache Spark is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 3.0.3 and earlier, 3.1.1 to 3.1.2, 3.2.0 to 3.2.1, <= 3.0.3, >= 3.1.1 <= 3.1.2, >= 3.2.0 <= 3.2.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2022-33891 Remediation Guide | SECUFOCUS NOW