[GHSA-4h8f-2wvx-gg5w] Bouncy Castle Java Cryptography API vulnerable to DNS poisoning #5717
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.
Updates
Comments
We are using the FIPS-TLS version of bc and were surprised that we were seemingly not affected by this vulnerability, when we actually were affected (verified by code inspection).
The official advisory (https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902024%E2%80%9034447) clearly says that BC FIPS TLS Java <=1.0.18 and also the LTS versions are affected, but none of the advisories (MITRE, GHSA, NVD, ...) reflect this.