{
  "@id": "urn:uuid:16022b5e-ac64-4ffc-822e-267d2af1de9b",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 6,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:10:25.284357+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2017-12972 does not affect version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2017-12972 describes an integer overflow vulnerability in byte-to-bit conversion during HMAC computation, allowing HMAC bypass attacks. The upstream vendor (Vladimir Dzhuvinov) fixed this in commit 0d2bd649 (June 2017) by adding ByteUtils.safeBitLength() with overflow checking. The target repository version 9.24.4-tuxcare.2 contains this fix - all critical crypto code paths (AAD.computeLength(), AESGCM validation, ContentCryptoProvider CEK checks, etc.) use safeBitLength(). The fix was already present in the upstream release before TuxCare onboarding (first TuxCare commit: f0f2e965). Verdict: not_affected because the vulnerable pattern (unsafe byte-to-bit conversion without overflow checking) is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.39), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35; = 4.36.1; = 4.37; = 4.37.1; = 4.38), Snyk (< 4.39).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12972"
      },
      "impact_statement": "CVE-2017-12972 describes an integer overflow vulnerability in byte-to-bit conversion during HMAC computation, allowing HMAC bypass attacks. The upstream vendor (Vladimir Dzhuvinov) fixed this in commit 0d2bd649 (June 2017) by adding ByteUtils.safeBitLength() with overflow checking. The target repository version 9.24.4-tuxcare.2 contains this fix - all critical crypto code paths (AAD.computeLength(), AESGCM validation, ContentCryptoProvider CEK checks, etc.) use safeBitLength(). The fix was already present in the upstream release before TuxCare onboarding (first TuxCare commit: f0f2e965). Verdict: not_affected because the vulnerable pattern (unsafe byte-to-bit conversion without overflow checking) is not present in the target.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.39), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35; = 4.36.1; = 4.37; = 4.37.1; = 4.38), Snyk (< 4.39)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T04:42:00.171839+00:00",
      "status_notes": "Vulnerability CVE-2017-12973 does not affect version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. not_affected \u2014 CVE-2017-12973 is NOT present in nimbus-jose-jwt version 9.24.4. The vulnerability (padding oracle attack via improper handling after invalid HMAC detection in authenticated AES-CBC decryption) was fixed by upstream commit 6a29f10f authored by Vladimir Dzhuvinov. This fix was already included in the upstream release 9.24.4 that TuxCare onboarded, prior to any TuxCare modifications. Both vulnera...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12973"
      },
      "impact_statement": "not_affected \u2014 CVE-2017-12973 is NOT present in nimbus-jose-jwt version 9.24.4. The vulnerability (padding oracle attack via improper handling after invalid HMAC detection in authenticated AES-CBC decryption) was fixed by upstream commit 6a29f10f authored by Vladimir Dzhuvinov. This fix was already included in the upstream release 9.24.4 that TuxCare onboarded, prior to any TuxCare modifications. Both vulnera..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2017-12974 does not affect version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. The target repository (nimbus-jose-jwt version 9.24.4-tuxcare.2) is NOT AFFECTED by CVE-2017-12974. The vulnerability\u2014accepting EC public key coordinates not mathematically on the declared elliptic curve, enabling Invalid Curve Attack\u2014was fixed in upstream version 4.36 (April 2017) by commit f3a7a801f0c6b078899fed9226368eb7b44e2b2f authored by Vladimir Dzhuvinov. This fix was already present in the upstream release 9.24.4 that TuxCare onboarded. All ECKey constructors now validate that x,y coordinates satisfy the elliptic curve equation (y^2) mod p = (x^3 + ax + b) mod p via ECChecks.isPointOnCurve(), rejecting invalid points at construction time.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.36), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35), Snyk (< 4.36).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12974"
      },
      "impact_statement": "The target repository (nimbus-jose-jwt version 9.24.4-tuxcare.2) is NOT AFFECTED by CVE-2017-12974. The vulnerability\u2014accepting EC public key coordinates not mathematically on the declared elliptic curve, enabling Invalid Curve Attack\u2014was fixed in upstream version 4.36 (April 2017) by commit f3a7a801f0c6b078899fed9226368eb7b44e2b2f authored by Vladimir Dzhuvinov. This fix was already present in the upstream release 9.24.4 that TuxCare onboarded. All ECKey constructors now validate that x,y coordinates satisfy the elliptic curve equation (y^2) mod p = (x^3 + ax + b) mod p via ECChecks.isPointOnCurve(), rejecting invalid points at construction time.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 4.36), NVD (= 1.0; = 1.1; = 1.2; = 1.3; = 1.4; = 1.5; = 1.6; = 1.7; = 1.8; = 1.9; = 1.9.1; = 1.10; = 1.11; = 1.12; = 2.0; = 2.0.1; = 2.1; = 2.1.1; = 2.2; = 2.3; = 2.4; = 2.5; = 2.6; = 2.7; = 2.8; = 2.9; = 2.10; = 2.10.1; = 2.11.0; = 2.12.0; = 2.13.0; = 2.13.1; = 2.14; = 2.15; = 2.15.1; = 2.15.2; = 2.16; = 2.17; = 2.17.1; = 2.17.2; = 2.18; = 2.18.1; = 2.18.2; = 2.19; = 2.19.1; = 2.20; = 2.21; = 2.22; = 2.22.1; = 2.23; = 2.24; = 2.25; = 2.26; = 2.26.1; = 3.0; = 3.1; = 3.1.1; = 3.1.2; = 3.2; = 3.2.1; = 3.2.2; = 3.3; = 3.4; = 3.5; = 3.6; = 3.7; = 3.8; = 3.8.1; = 3.8.2; = 3.9; = 3.9.1; = 3.9.2; = 3.10; = 4.0; = 4.0.1; = 4.1; = 4.1.1; = 4.2; = 4.3; = 4.3.1; = 4.4; = 4.5; = 4.6; = 4.7; = 4.8; = 4.9; = 4.10; = 4.11; = 4.11.1; = 4.11.2; = 4.12; = 4.13; = 4.13.1; = 4.14; = 4.15; = 4.15.1; = 4.16; = 4.16.1; = 4.16.2; = 4.17; = 4.18; = 4.19; = 4.20; = 4.21; = 4.22; = 4.23; = 4.24; = 4.25; = 4.26; = 4.26.1; = 4.27; = 4.27.1; = 4.28; = 4.29; = 4.30; = 4.31; = 4.31.1; = 4.32; = 4.33; = 4.34; = 4.34.1; = 4.34.2; = 4.35), Snyk (< 4.36)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:01:00.133094+00:00",
      "status_notes": "Vulnerability CVE-2019-17195 does not affect version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2019-17195 affects Connect2id Nimbus JOSE+JWT before v7.9. The target version 9.24.4 (released 2022-09-09) is significantly after v7.9 (released 2019-10-05) and already contains all upstream fixes for this CVE. The fixes include proper exception handling in JSONObjectUtils.parse and null checks for JOSE header parameters (alg, typ, crit, jwk, zip, Base64URL-encoded parameters). All fix commits were authored by the upstream vendor (Vladimir Dzhuvinov) and were present in the upstream version 9.24.4 before TuxCare onboarded it.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 7.9), NVD (< 7.9), Snyk (< 7.8.1).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-17195"
      },
      "impact_statement": "CVE-2019-17195 affects Connect2id Nimbus JOSE+JWT before v7.9. The target version 9.24.4 (released 2022-09-09) is significantly after v7.9 (released 2019-10-05) and already contains all upstream fixes for this CVE. The fixes include proper exception handling in JSONObjectUtils.parse and null checks for JOSE header parameters (alg, typ, crit, jwk, zip, Base64URL-encoded parameters). All fix commits were authored by the upstream vendor (Vladimir Dzhuvinov) and were present in the upstream version 9.24.4 before TuxCare onboarded it.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 7.9), NVD (< 7.9), Snyk (< 7.8.1)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2023-52428 is fixed in version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2023-52428"
      }
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.24.4-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53864 affects version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2025-53864"
      },
      "action_statement": "Vulnerability CVE-2025-53864 affects version 9.24.4-tuxcare.1 of com.nimbusds:nimbus-jose-jwt."
    }
  ]
}
