Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE related security updates for PySpark and PyArrow #2229

Merged

Conversation

astimoore
Copy link

Type of PR

  • BUG
  • FEAT
  • MAINT
  • DOC

Give a brief description for the solution you have provided

Our SecOps team has identified four security alerts following a recent scan of splink, related to the versioning of two package dependencies (pyspark, pyarrow). I've outlined these alerts below, and linked CVE codes to pages in the National Security Database:

CVE Name Severity Package Name Package Version Fixed Version CVE Published Date
CVE-2021-38296 High pyspark 3.1.2 3.1.3 2022 Mar 10
CVE-2022-33891 High pyspark 3.1.2 3.2.2 2022 Jul 18
CVE-2023-32007 High pyspark 3.1.2 3.2.2 2023 May 02
CVE-2023-47248 Critical pyarrow 13.0.0 14.0.1 2023 Nov 09

Unfortunately, these vulnerabilities currently prevent us from safely utilizing this package in our production environment.

This pull request aims to resolve these issues to ensure compliance with our security standards and maintain the integrity of our systems. It updates two files benchmarking/requirements.txt and binder/requirements.txt with secure versions of pyspark (3.2.2) and pyarrow (14.0.1).

Copy link
Member

@RobinL RobinL left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks very much!

@RobinL RobinL merged commit 955a390 into moj-analytical-services:master Jul 3, 2024
2 checks passed
@astimoore astimoore deleted the cve-related-security-updates branch July 3, 2024 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants