{
  "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.6",
  "serialNumber": "urn:uuid:95de04dc-17fa-5a23-b016-7f4553ed3ea5",
  "version": 1,
  "metadata": {
    "supplier": {
      "name": "TuxCare",
      "url": [
        "https://tuxcare.com"
      ]
    }
  },
  "components": [
    {
      "name": "bctls-jdk14",
      "purl": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7",
      "type": "library",
      "group": "org.bouncycastle",
      "bom-ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7",
      "version": "1.78.1-tuxcare.7",
      "pedigree": {
        "ancestors": [
          {
            "name": "bctls-jdk14",
            "purl": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1",
            "type": "library",
            "group": "org.bouncycastle",
            "version": "1.78.1"
          }
        ]
      },
      "supplier": {
        "url": [
          "https://tuxcare.com"
        ],
        "name": "TuxCare"
      }
    }
  ],
  "vulnerabilities": [
    {
      "id": "CVE-2024-29857",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7"
        }
      ],
      "bom-ref": "urn:uuid:7630b8b2-abe8-5358-8998-8d73e429b4e6",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-29857 does not affect version 1.78.1-tuxcare.7 of org.bouncycastle:bctls-jdk14. Target version 1.78.1 is not affected by CVE-2024-29857. The vulnerability (excessive CPU consumption from unbounded F2m field size parameters) was fixed in upstream Bouncy Castle version 1.78, and the target has this fix in the main production code. The fix adds a bounds check (max 1142, twice 571) on the F2m field size parameter 'm' in the buildField method (ECCurve.java:848-851), throwing IllegalArgumentException if exceeded. This fix was authored by upstream developer David Hook (dgh@cryptoworkshop.com) and shipped with the upstream 1.78 release, before TuxCare onboarded version 1.78.1 (first TuxCare commit 2ef4cebd). Note: Legacy JDK 1.2 and J2ME compatibility builds lack the fix, but these target obsolete platforms (JDK 1.2 from 1998, J2ME from 2000s) rarely used in modern deployments.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 1.78; < 1.78; < 1.78; < 1.78; < 1.78; < 1.78), cve.org (<= 1.77), Snyk (< 1.78; < 1.78).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-30171",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7"
        }
      ],
      "bom-ref": "urn:uuid:be576683-9e2f-501f-9fee-656142b5f6d5",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30171 does not affect version 1.78.1-tuxcare.7 of org.bouncycastle:bctls-jdk14. not_affected \u2014 CVE-2024-30171 (timing-based leakage in RSA handshakes) is NOT present in bc-java 1.78.1. The vulnerability existed in versions before 1.78, but the target is version 1.78.1 which already contains the upstream timing-safe fix authored by Peter Dettman (peter.dettman@bouncycastle.org) in commit 98b18399b. The fix was shipped in the upstream 1.78.1 release that TuxCare onboarded, making this vers...",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2024-30172",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7"
        }
      ],
      "bom-ref": "urn:uuid:8af46006-7b20-5082-bbac-350f0814d955",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2024-30172 does not affect version 1.78.1-tuxcare.7 of org.bouncycastle:bctls-jdk14. CVE-2024-30172 describes an infinite loop vulnerability in Ed25519/Ed448 signature verification in Bouncy Castle Java versions 1.73-1.77. The target repository at version 1.78.1-tuxcare.9 already contains the upstream fixes (commits 9c165791b and ebe1c7557) that were shipped in the upstream 1.78.1 release. The fix adds iteration counters to the reduceBasisVar methods, limiting loops to TARGET_LENGTH * 4 iterations and returning false on timeout, causing verification to throw IllegalStateException instead of looping infinitely. Both fix commits were authored by upstream developers (alexander.scheel@keyfactor.com, peter.dettman@bouncycastle.org) and are ancestors of the first TuxCare onboarding commit (2ef4cebdee0579b2f8db62334d08bc5aec1ecd67), confirming they were part of the upstream 1.78.1 release before TuxCare's Extended Lifecycle Support maintenance began. The target is not vulnerable because the vulnerable code pattern has been removed by the upstream vendor fix.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78; >= 1.73, < 1.78), Snyk (>= 1.71, < 1.78; >= 1.71, < 1.78).",
        "justification": "code_not_present"
      }
    },
    {
      "id": "CVE-2025-8885",
      "affects": [
        {
          "ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7"
        }
      ],
      "bom-ref": "urn:uuid:6941f701-80d6-5134-a5e1-8c31da7047c1",
      "analysis": {
        "state": "not_affected",
        "detail": "Vulnerability CVE-2025-8885 does not affect version 1.78.1-tuxcare.7 of org.bouncycastle:bctls-jdk14. not_affected \u2014 The target version 1.78.1-tuxcare.9 is not affected by CVE-2025-8885. The vulnerability fix (adding 4096-byte limit on OID contents) was already present in the upstream Bouncy Castle 1.78.1 release that TuxCare onboarded. The fix commit 3790993df5d28f661a64439a8664343437ed3865 by peter.dettman@bouncycastle.org is an ancestor of both the TuxCare onboarding commit and the target HEAD. The defensi...",
        "justification": "code_not_present"
      }
    }
  ],
  "dependencies": [
    {
      "ref": "pkg:maven/org.bouncycastle/bctls-jdk14@1.78.1-tuxcare.7"
    }
  ]
}