CVE-2016-1000346: Bouncycastle Bc-Java vulnerability
Bouncycastle · Bc-Java
Vendor fix available · Affected: Bouncycastle Bc-Java · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 82% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Bouncycastle
- Published
- June 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2016-1000346 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-320cwe.mitre.org
- Vendor advisoryaccess.redhat.com
- Vendor advisoryusn.ubuntu.com
- Vendor advisoryaccess.redhat.com
- oracle.com/security-alerts/cpuoct2020.htmloracle.com
- security.netapp.com/advisory/ntap-20181127-0004security.netapp.com
- github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714cgithub.com
- Mailing listlists.debian.org