← Back
CVE-2022-33891
CISA KEV
high
[KEV] OS Command Injection in Apache pyspark (CVE-2022-33891)
Summary
OS command injection in Apache pyspark (CVE-2022-33891). Successful exploitation can lead to full system takeover. Exploitable via ``spark.acls.enable``. Listed in CISA KEV — actively exploited. Mitigation: upgrade to `3.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-33891** has been found in Apache pyspark.
Attackers can target a specific entry point like ``spark.acls.enable`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
Note: CISA has officially confirmed this is **actively exploited in the wild**. Treat it with elevated urgency.
What to do: upgrade Apache pyspark to **3.2.2** or later.
If unsure, ask your IT team or search "Apache pyspark CVE-2022-33891" on the vendor's site.
CVE-2022-33891 (Apache pyspark) — CWE-78 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `spark.acls.enable`
Patched: `3.2.2` — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**OS command injection** (CWE-78) exists in Apache pyspark. Attackers reach the vulnerable code path via ``spark.acls.enable`` without authentication.
📍 Affected scope
Apache pyspark — . Attack surface: `spark.acls.enable`.
🔥 Severity
Severity: High. Successful exploitation can lead to full system takeover **Listed in CISA KEV** — actively exploited in the wild, treat as top priority.
🔧 How to fix
Update to **3.2.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pyspark' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pyspark' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pyspark` を grep し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade pyspark to 3.2.2ステージング環境で 3.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pyspark
[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"3.2.2"}]}]
maven
org.apache.spark:spark-parent_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"3.1.1"},{"fixed":"3.2.2"}]}]
pip
pyspark
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-33891
- package https://github.com/apache/spark
- web https://lists.apache.org/thread/p847l3kopoo5bjtmxrcwk21xp6tjxqlc
- web https://github.com/advisories/GHSA-4x9r-j582-cgr8
- web https://github.com/pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2022-236.yaml
- web https://packetstormsecurity.com/files/168309/Apache-Spark-Unauthenticated-Command-Injection.html
- web https://www.openwall.com/lists/oss-security/2023/05/02/1
- web http://packetstormsecurity.com/files/168309/Apache-Spark-Unauthenticated-Command-Injection.html
- web http://www.openwall.com/lists/oss-security/2023/05/02/1
- web https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-33891