# CVE-2018-1334: Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark > Local users can connect to Spark applications and impersonate the running user, leading to privilege escalation and data access. - **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jul 2018 - **Updated:** 17 Sep 2024 - **Also known as:** GHSA-6mqq-8r44-vmjc, PYSEC-2018-25 ## What is CVE-2018-1334? CVE-2018-1334 is a medium-severity authentication bypass vulnerability in Apache Spark, published on 12 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In Apache Spark 1.0.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, when using PySpark or SparkR, it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2018-1334? 15 open source packages ship an affected version, including org.apache.spark:spark-core_2.11, org.apache.spark:spark-core_2.10 and pyspark. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.spark:spark-core_2.11` | Maven | From 1.0.0 | 2.1.3 | | `org.apache.spark:spark-core_2.11` | Maven | From 1.0.0 | 2.1.3 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.3.0 | 2.3.1 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.3.0 | 2.3.1 | | `org.apache.spark:spark-core_2.10` | Maven | From 1.0.0 | 2.1.3 | | `org.apache.spark:spark-core_2.10` | Maven | From 1.0.0 | 2.1.3 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.2.0 | 2.2.2 | | `pyspark` | PyPI | All versions | 2.1.3 | | `pyspark` | PyPI | All versions | 2.1.3 | | `pyspark` | PyPI | From 2.2.0 | 2.2.2, 2.1.3 | | `pyspark` | PyPI | From 2.2.0 | 2.2.2 | | `pyspark` | PyPI | From 2.2.0 | 2.2.2 | Products: Apache Spark. ## How do I fix CVE-2018-1334? Upgrade org.apache.spark:spark-core_2.11 to a fixed version for your release line: 2.1.3, 2.2.2 or 2.3.1. ## Is CVE-2018-1334 being exploited? There is no known exploitation of CVE-2018-1334 in the wild and no public exploit code. ## Other vulnerabilities in Apache Spark - [CVE-2022-33891](https://insights.sbomify.com/CVE-2022-33891/): Apache Spark Command Injection (high 8.8, exploited in the wild) - [CVE-2020-9480](https://insights.sbomify.com/CVE-2020-9480/): Improper Authentication in Apache Spark (critical 9.8) - [CVE-2018-17190](https://insights.sbomify.com/CVE-2018-17190/): Remote Code Execution in spark-core (critical 9.8) - [CVE-2019-20445](https://insights.sbomify.com/CVE-2019-20445/): HTTP Request Smuggling in Netty (critical 9.1) - [CVE-2025-54920](https://insights.sbomify.com/CVE-2025-54920/): Apache Spark: Spark History Server Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-1334 and fix it if it is affected. What it is: CVE-2018-1334 is a medium-severity authentication bypass vulnerability in Apache Spark, published on 12 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-1334 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.spark:spark-core_2.11 (Maven): affected from 1.0.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.11 (Maven): affected from 1.0.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.3.0; fixed in 2.3.1 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.3.0; fixed in 2.3.1 - org.apache.spark:spark-core_2.10 (Maven): affected from 1.0.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.10 (Maven): affected from 1.0.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.2.0; fixed in 2.2.2 - pyspark (PyPI): affected all versions; fixed in 2.1.3 - pyspark (PyPI): affected all versions; fixed in 2.1.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-1334/ (Markdown: https://insights.sbomify.com/CVE-2018-1334/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1334 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1334 - OSV: https://osv.dev/vulnerability/CVE-2018-1334 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-1334/ Summaries are generated and may contain mistakes; the official description above is the record.