How many CVEs have patched getCause?

1 published CVEs changed getCause in bcgit/bc-java, in 1 distinct patches totalling 10 changed lines, between 2018 and 2018.

What is the latest CVE that changed getCause?

CVE-2016-1000345 (Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15), published 2018-06-04, changed lines 532 to 534 of prov/src/main/java/org/bouncycastle/jcajce/provider/asymmetric/rsa/CipherSpi.java.

How does getCause compare to the rest of bcgit/bc-java?

bcgit/bc-java has 73 CVEs with a located fix in total; 1 of them changed getCause.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

bcgit/bc-java

Function

getCause

Name: getCause in bcgit/bc-java: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

prov/src/main/java/org/bouncycastle/jcajce/provider/asymmetric/rsa/CipherSpi.java

Last patched June 4, 2018

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

10

Lines changed

Added plus removed

2018

Years

By CVE publication date

Overview

getCause in bcgit/bc-java was changed by 1 published CVE fixes in 2018, in 1 distinct patches that added or removed 10 lines in total.

bcgit/bc-java has 73 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed getCause, newest first, with the lines each fix touched.

Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
CVE-2016-1000345 · lines 532–534 · +2 −8
Medium · CVSS 5.9
EPSS 2.6%2018-06-04

Get an alert when the next CVE fix lands in bcgit/bc-java, with the patched functions.

Monitor bc-java CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in bcgit/bc-java changed by the most CVE fixes.

engineDoFinal3 CVEs · prov/src/main/java/org/bouncycastle/jcajce/provider/asymmetric/dh/IESCipher.java checkNameConstraints2 CVEs · pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java processPacket2 CVEs · core/src/main/java/org/bouncycastle/crypto/modes/KCCMBlockCipher.java checkNameConstraints2 CVEs · prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.java readBlock2 CVEs · pg/src/main/java/org/bouncycastle/openpgp/operator/bc/BcAEADUtil.java readBlock2 CVEs · pg/src/main/java/org/bouncycastle/openpgp/operator/jcajce/JceAEADUtil.java

All patched functions in bcgit/bc-java

Frequently asked questions

Common questions about CVE fixes to getCause.

How many CVEs have patched getCause?: 1 published CVEs changed getCause in bcgit/bc-java, in 1 distinct patches totalling 10 changed lines, between 2018 and 2018.
What is the latest CVE that changed getCause?: CVE-2016-1000345 (Moderate severity vulnerability that affects org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15), published 2018-06-04, changed lines 532 to 534 of prov/src/main/java/org/bouncycastle/jcajce/provider/asymmetric/rsa/CipherSpi.java.
How does getCause compare to the rest of bcgit/bc-java?: bcgit/bc-java has 73 CVEs with a located fix in total; 1 of them changed getCause.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track bcgit/bc-java CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing