CVE-2022-33891

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Apache Spark. For every flaw being used in attacks, see Exploited flaws; for Apache’s, see Apache flaws being used in attacks.

CVE-2022-33891 is a security flaw in Apache Spark, open-source software from the Apache Software Foundation. Attackers can run commands on Apache Spark. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 7 Mar 2023.[1]

Apache Spark is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Apache has published a fix or advice.

Description

CISA calls it a command injection in Apache Spark. In its words: “Apache Spark contains a command injection vulnerability via Spark User Interface (UI) when Access Control Lists (ACLs) are enabled.”[1]

The CVE record adds: “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 currently running as. This affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1.”[2]

The underlying weakness is OS command injection (CWE-78), in MITRE’s list of common software weaknesses.

It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Apache’s advisory has them[3]. CISA names the product as Apache Spark.

Most families won’t have Apache Spark; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 7 Mar 2023, 232 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 28 Mar 2023 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 93%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Apache has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Check whether you use it.Apache Spark is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 28 Mar 2023 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 93%.[4]

See also

Other Apache flaws

  • CVE-2016-3081, Apache Struts: command injection ·
  • CVE-2026-34486, Apache Tomcat: missing encryption of sensitive data ·
  • CVE-2026-34197, Apache ActiveMQ: improper input validation ·
  • CVE-2024-38475, Apache HTTP Server: improper escaping of output ·
  • CVE-2025-24813, Apache Tomcat: path equivalence ·

Other OS command injection flaws

  • CVE-2026-110447, Collabora Online – Built-in CODE Server: online – built-in CODE server OS command injection ·
  • CVE-2026-106931, EG Secure Solutions SiteGuard Server Edition: OS command injection ·
  • CVE-2026-83549, SonicWall SMA1000 Appliances: OS command injection ·
  • CVE-2026-49869, Kestra OSS: OSS OS command injection ·
  • CVE-2026-73570, Synacor Zimbra Collaboration Suite (ZCS): OS command injection ·

Added the same day

  • CVE-2022-35914, Teclib GLPI: remote code execution ·
  • CVE-2022-28810, Zoho ManageEngine: aDSelfService plus remote code execution ·

Every Apache flaw on CISA’s list · Everything added in March 2023

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Apache Spark Command Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 7 Mar 2023.
  2. ^ National Institute of Standards and Technology. “CVE-2022-33891 Detail”. National Vulnerability Database, published 18 Jul 2022.
  3. ^ Apache. Advisories and fixes: lists.apache.org.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.932, percentile 99.8, 31 Oct 2026.
  5. CVE Program. “CVE-2022-33891”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.