Migrate from BouncyCastle bcpkix-jdk15on
to bcpkix-jdk18on
to Address Security Vulnerabilities
#58
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.
This pull request contributes to the security and modernization of the project by migrating the BouncyCastle dependency from
org.bouncycastle:bcpkix-jdk15on
toorg.bouncycastle:bcpkix-jdk18on
version1.78.1
. The migration to thejdk18on
variant ensures compatibility with newer Java versions and introduces important security enhancements.Key Changes:
Dependency Migration: The existing
bcpkix-jdk15on
dependency has been replaced withbcpkix-jdk18on
. This update leverages the latest improvements and security fixes provided by BouncyCastle for Java 18 and above, aligning the project with modern cryptographic practices.Security Vulnerability Fixes: By upgrading to
bcpkix-jdk18on
version1.78.1
, this contribution addresses several security vulnerabilities that were present in the olderjdk15on
version.Resolved CVEs:
This migration specifically addresses the following Common Vulnerabilities and Exposures (CVEs) that affected the previous version of BouncyCastle:
Impact:
This contribution significantly enhances the security and future-proofing of the project by migrating to a more modern and secure cryptographic library. The upgrade is essential for protecting the project from known vulnerabilities and ensuring compatibility with the latest Java versions.