Skip to content

← Public intelligence

Maven package

org.bouncycastle:bcprov-jdk12

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.9MavenPublished

    Bouncy Castle Java Cryptography API vulnerable to DNS poisoning

    CVE-2024-34447 · GHSA-4h8f-2wvx-gg5w

    Affected
    • Maven org.bouncycastle:bcprov-jdk12 >= 1.61, < 1.78
    Fixed in
    1.78· Vendor fix available
    Issue
    An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.6) and before BC FIPS TLS Java 1.0.19. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be performed against a DNS-resolved IP address in some situations, opening up a possibility of DNS poisoning.

    Recommended action: Upgrade to 1.78 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →