bouncycastle: lack of class checking in deserialization of XMSS/XMSS^MT private keys with BDS state information
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4446-656p-f54g | Deserialization of Untrusted Data in Bouncy castle |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 4.8% (4.767% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bouncycastle bc-java
|
|
| CPEs | cpe:2.3:a:bouncycastle:bc-java:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Bouncycastle legion-of-the-bouncy-castle-java-crytography-api
|
Bouncycastle bc-java
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')