PYSEC-2022-186

    Dashboard / Vulnerabilities / PYSEC-2022-186

    PYSEC-2022-186

    Published: 10 Mar 2022Last Modified: 6 Dec 2023

    Summary:

    Details: Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later

    References: https://lists.apache.org/thread/70x8fw2gx3g9ty7yk0f2f1dlpqml2smd, https://github.com/advisories/GHSA-9rr6-jpg7-9jg6

    Affected packages

    Package

    Name: pyspark

    Purl: pkg:pypi/pyspark

    Affected ranges

    Type: ECOSYSTEM

    Events:

    Introduced- 0
    Fixed -3.1.3

    Affected versions

    2.1.1
    2.1.2
    2.1.3

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High