In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| bouncycastle | legion-of-the-bouncy-castle-java-crytography-api | 1.38 - 1.56 | - |
| redhat | satellite | - | - |
| redhat | satellite_capsule |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
5
Affected Products
16
References
bouncycastle / legion-of-the-bouncy-castle-java-crytography-api
| - |
| - |
| canonical | ubuntu_linux | - | - |
| netapp | 7-mode_transition_tool | - | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploitability
Impact