Find, fix and prevent vulnerabilities in your code.
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.70
Detailed paths
-
Introduced through: ketola/jlibra@ketola/jlibra#85a0c314c50c813d04c546e65e8c553a4a22360e › org.bouncycastle:bcprov-jdk15on@1.70
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') within the org.bouncycastle.openssl.PEMParser
class. Parsing a file that has crafted ASN.1
data through the PEMParser
causes an OutOfMemoryError
.
Workaround
The attack can be avoided by filtering PEM
requests containing EXTERNAL
tagged encodings.
Remediation
There is no fixed version for org.bouncycastle:bcprov-jdk15on
.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.70
Detailed paths
-
Introduced through: ketola/jlibra@ketola/jlibra#85a0c314c50c813d04c546e65e8c553a4a22360e › org.bouncycastle:bcprov-jdk15on@1.70
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the solveQuadraticEquation()
function used for certificate verification in ECCurve.java
. Passing a large f2m parameter can cause excessive CPU consumption.
Remediation
There is no fixed version for org.bouncycastle:bcprov-jdk15on
.
References
medium severity
- Vulnerable module: org.bouncycastle:bcprov-jdk15on
- Introduced through: org.bouncycastle:bcprov-jdk15on@1.70
Detailed paths
-
Introduced through: ketola/jlibra@ketola/jlibra#85a0c314c50c813d04c546e65e8c553a4a22360e › org.bouncycastle:bcprov-jdk15on@1.70
Overview
org.bouncycastle:bcprov-jdk15on is a Java implementation of cryptographic algorithms.
Affected versions of this package are vulnerable to Information Exposure due to missing validation for the X.500 name of any certificate, subject, or issuer. The presence of a wild card may lead to information disclosure. This could allow a malicious user to obtain unauthorized information via blind LDAP Injection, exploring the environment and enumerating data.
Note:
The exploit depends on the structure of the target LDAP directory as well as what kind of errors are exposed to the user.
Remediation
A fix was pushed into the master
branch but not yet published.