CyberRota Analysis
AI-GeneratedThe vulnerability lies in the improper verification of cryptographic signatures within the attribute certificate path validator of the Bouncy Castle library, allowing remote attackers to exploit forged X.509 attribute certificates. This could enable unauthorized access to roles or privileges granted by applications relying on these certificates for validation. Organizations utilizing affected versions of the Bouncy Castle library for attribute certificate validation should prioritize patching to mitigate potential exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Improper verification of cryptographic signature in the attribute certificate path validator (PkixAttrCertPathValidator, also used by PkixAttrCertPathBuilder) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote attacker to have a forged X.509 attribute certificate accepted as valid, and so obtain whatever roles or privileges an application grants on the strength of its attributes, via an attribute certificate that names a trusted attribute authority as its issuer but was not signed by it, because the RFC 3281 validation steps check the holder and issuer certification paths, validity period, extensions and revocation status but never verify the attribute certificate's signature with the issuer's public key. Only applications that use these classes to validate attribute certificates are affected.