CVE related security updates for PySpark and PyArrow #2229
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of PR
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: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
andbinder/requirements.txt
with secure versions ofpyspark
(3.2.2) andpyarrow
(14.0.1).