An issue was discovered in the FIPS Java API of Bouncy Castle BC-FJA before 1.0.2.4. Changes to the JVM garbage collector in Java 13 and later trigger an issue in the BC-FJA FIPS modules where it is possible for temporary keys used by the module to be zeroed out while still in use by the module, resulting in errors or potential information loss. NOTE: FIPS compliant users are unaffected because the FIPS certification is only for Java 7, 8, and 11.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Fips_java_api | Bouncycastle | * | 1.0.2.4 (excluding) |
| Bouncycastle | Ubuntu | bionic | * |
| Bouncycastle | Ubuntu | focal | * |
| Bouncycastle | Ubuntu | kinetic | * |
| Bouncycastle | Ubuntu | lunar | * |
| Bouncycastle | Ubuntu | mantic | * |
| Bouncycastle | Ubuntu | oracular | * |
| Bouncycastle | Ubuntu | trusty | * |
| Bouncycastle | Ubuntu | xenial | * |