Skip to content

chore: upgrade to latest bouncycastle - #51

Merged
lfarrel6 merged 7 commits into
masterfrom
liam/upgrade-bouncycastle-provider-to-jdk18on
Jul 17, 2026
Merged

chore: upgrade to latest bouncycastle#51
lfarrel6 merged 7 commits into
masterfrom
liam/upgrade-bouncycastle-provider-to-jdk18on

Conversation

@lfarrel6

Copy link
Copy Markdown
Member

Why

dependency on the bouncy castle library was stale and due a patch.

How

Migrate from bcprov-jdk15on to bcprov-jdk18on to resolve several vulns.

@socket-security

socket-security Bot commented Jul 16, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedmaven/​org.bouncycastle/​bcprov-jdk18on@​1.84361009010080
Addedmaven/​org.slf4j/​slf4j-nop@​1.7.3410010090100100

View full report

@socket-security

socket-security Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: maven org.bouncycastle:bcprov-jdk18on is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: lib/gradle.lockfilemaven/org.bouncycastle/bcprov-jdk18on@1.84

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.bouncycastle/bcprov-jdk18on@1.84. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

lfarrel6 and others added 4 commits July 16, 2026 15:06
…load

Introduce a public InvalidCipherException(Throwable) constructor that
preserves the cause chain, and deprecate the BouncyCastle-typed
constructor which leaked BC into the SDK's public API. Switch the sole
internal caller (EncryptionService) to the new overload via a Throwable
cast so overload resolution binds to the non-deprecated variant. The
deprecated constructor is retained for binary compatibility and
scheduled for removal in v5.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PwN3TUtjUNTobcWKt8dZH4
…b.com:evervault/evervault-java into liam/upgrade-bouncycastle-provider-to-jdk18on
@lfarrel6
lfarrel6 marked this pull request as ready for review July 16, 2026 19:50
@lfarrel6
lfarrel6 requested a review from a team as a code owner July 16, 2026 19:50
@lfarrel6
lfarrel6 merged commit d0cd569 into master Jul 17, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants