org.bouncycastle:bcpg-jdk15on@1.65

  • latest version

    1.70

  • first published

    14 years ago

  • latest version published

    4 years ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the org.bouncycastle:bcpg-jdk15on package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Exposure of Sensitive Information Through Metadata

    Affected versions of this package are vulnerable to Exposure of Sensitive Information Through Metadata via CFB quick-check decryption oracle in the getDataStream() method of PGPSymmetricKeyEncryptedData, reached through PGPPBEEncryptedData, PGPSessionKeyEncryptedData, and OpenPGPMessageProcessor, which checks the two repeated CFB IV bytes and throws PGPDataValidationException before MDC verification completes. An attacker with adaptive chosen-ciphertext access to a decryption endpoint can recover roughly two plaintext bytes per about 2^15 queries by distinguishing the early quick-check failure from a later MDC or parse failure. This affects only the symmetric and session-key decryption paths on SEIPDv1 messages, not PGPPublicKeyEncryptedData which already skips the check, and it requires the endpoint's early and late failures to be distinguishable to the attacker.

    How to fix Exposure of Sensitive Information Through Metadata?

    There is no fixed version for org.bouncycastle:bcpg-jdk15on.

    [0,)
    • H
    Memory Allocation with Excessive Size Value

    Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value in the readPacket() method of UserAttributeSubpacketInputStream, which reads a 5-octet subpacket length up to Integer.MAX_VALUE and allocates new byte[bodyLen-1] after checking only against a limit derived from JVM maximum memory rather than the enclosing packet body length. An attacker can exhaust memory and trigger an OutOfMemoryError by getting a victim to import an OpenPGP public key whose user-attribute subpacket declares a length approaching the full heap, so a small key forces a near-heap-sized allocation. This requires the victim to import the attacker's public key, for example from a keyserver, WKD, or email attachment, and reaches the flaw through the single-argument UserAttributePacket stream construction where the limit is not bounded by the actual packet body.

    How to fix Memory Allocation with Excessive Size Value?

    There is no fixed version for org.bouncycastle:bcpg-jdk15on.

    [0,)