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

Updating bcprov-jdk18on to fix CVE-2024-29857 and other CVEs #357

Open
Skillzore opened this issue May 2, 2024 · 3 comments
Open

Updating bcprov-jdk18on to fix CVE-2024-29857 and other CVEs #357

Skillzore opened this issue May 2, 2024 · 3 comments

Comments

@Skillzore
Copy link

Just wondering if there are any plans to update the bouncycastle dependency to the latest version 1.78.1 to get rid of the CVEs present in the current version of the dependency?

For reference, see Security Advisories in the bouncycastle release notes here.

@mbechler
Copy link
Contributor

mbechler commented May 3, 2024

Unless there is a binary or source incompatibility preventing people from upgrading - I'm not going to do releases just to bump the pom version - consumers can just override the version and management of runtime dependency versions generally is up to them.

@miroslavvojtus
Copy link

  1. thanks for your work.
  2. this is pretty unfortunate approach. It is common practice that library maintainer maintains safe dependencies if it uses dependency management tools. This way we are making vulnerable whole the community. It is like why should thousands dependent projects make hack if only one the depended may do it right.

@mbechler
Copy link
Contributor

mbechler commented Jul 17, 2024

What you are implying is that 100eds to thousands of library maintainers should push "empty" releases each time if a dependency makes a compatible release - with all due respect - this would be a complete waste of time for everybody.

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

No branches or pull requests

3 participants