Affected versions
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
In Bouncy Castle for Java before 1.85, BKS/UBER keystore allocates from untrusted lengths before integrity check. This issue also affects Bouncy Castle for Java LTS before 2.73.12.
A flaw was found in Bouncy Castle for Java. The BKS/UBER keystore component allocates memory based on untrusted length values before performing an integrity check. A remote attacker could exploit this vulnerability by providing a specially crafted keystore, leading to excessive memory allocation and a denial of service (DoS) condition.

