PYSEC-2022-186

See a problem?
Import Source
https://github.com/pypa/advisory-database/blob/main/vulns/pyspark/PYSEC-2022-186.yaml
JSON Data
https://api.test.osv.dev/v1/vulns/PYSEC-2022-186
Aliases
Published
2022-03-10T09:15:00Z
Modified
2023-12-06T00:46:23.890022Z
Summary
[none]
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

Affected packages

PyPI / pyspark

Package

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
3.1.3

Affected versions

2.*

2.1.1
2.1.2
2.1.3
2.2.0
2.2.1
2.2.2
2.2.3
2.3.0
2.3.1
2.3.2
2.3.3
2.3.4
2.4.0
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8

3.*

3.0.0
3.0.1
3.0.2
3.0.3
3.1.1
3.1.2