{
  "@id": "urn:uuid:db07452d-2e3b-425f-b73f-d4a2b4f697ba",
  "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.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2017-12972 does not affect version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt. CVE-2017-12972 (integer overflow in byte-to-bit conversion enabling HMAC bypass) is NOT present in target version 9.22-tuxcare.2. The upstream vendor (Connect2id) fixed this vulnerability in version 4.39 (commit 0d2bd649, June 2017) by introducing overflow-safe bit length computation. The fix includes: (1) new IntegerOverflowException class, (2) ByteUtils.safeBitLength() methods that compute byte*8 as long and verify result fits in int range, (3) replacement of all unsafe bitLength() calls with safeBitLength() in AAD.computeLength() and other crypto paths. Target version 9.22 (released 2021) includes this upstream fix as part of the base release TuxCare onboarded. The vulnerable pattern (unchecked multiplication that allows integer overflow to bypass HMAC validation by shifting AAD/ciphertext) 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 (integer overflow in byte-to-bit conversion enabling HMAC bypass) is NOT present in target version 9.22-tuxcare.2. The upstream vendor (Connect2id) fixed this vulnerability in version 4.39 (commit 0d2bd649, June 2017) by introducing overflow-safe bit length computation. The fix includes: (1) new IntegerOverflowException class, (2) ByteUtils.safeBitLength() methods that compute byte*8 as long and verify result fits in int range, (3) replacement of all unsafe bitLength() calls with safeBitLength() in AAD.computeLength() and other crypto paths. Target version 9.22 (released 2021) includes this upstream fix as part of the base release TuxCare onboarded. The vulnerable pattern (unchecked multiplication that allows integer overflow to bypass HMAC validation by shifting AAD/ciphertext) 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.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-03T04:42:16.705744+00:00",
      "status_notes": "Vulnerability CVE-2017-12973 does not affect version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt. not_affected \u2014 CVE-2017-12973 (padding oracle attack in authenticated AES-CBC decryption) is NOT present in nimbus-jose-jwt version 9.22. The fix commit 6a29f10f from June 2017 by upstream author Vladimir Dzhuvinov shipped in the upstream release before TuxCare's maintenance began. Both authenticated decryption methods (decryptAuthenticated and decryptWithConcatKDF) check the MAC FIRST and throw immediately i...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12973"
      },
      "impact_statement": "not_affected \u2014 CVE-2017-12973 (padding oracle attack in authenticated AES-CBC decryption) is NOT present in nimbus-jose-jwt version 9.22. The fix commit 6a29f10f from June 2017 by upstream author Vladimir Dzhuvinov shipped in the upstream release before TuxCare's maintenance began. Both authenticated decryption methods (decryptAuthenticated and decryptWithConcatKDF) check the MAC FIRST and throw immediately i..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2017-12974 does not affect version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt. Target version 9.22 is not affected by CVE-2017-12974. The vulnerability was fixed in upstream version 4.36 (April 2017) by commit f3a7a801, which added EC curve validation to prevent Invalid Curve Attacks. This fix was already present in the upstream 9.22 release that TuxCare onboarded. The target contains the complete fix: ECChecks.isPointOnCurve() validates the curve equation (y^2 mod p = x^3 + ax + b mod p) in all ECKey constructors (lines 725, 794, 864), ECDHDecrypter (lines 255, 259), and ECDSAVerifier (line 128).\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": "Target version 9.22 is not affected by CVE-2017-12974. The vulnerability was fixed in upstream version 4.36 (April 2017) by commit f3a7a801, which added EC curve validation to prevent Invalid Curve Attacks. This fix was already present in the upstream 9.22 release that TuxCare onboarded. The target contains the complete fix: ECChecks.isPointOnCurve() validates the curve equation (y^2 mod p = x^3 + ax + b mod p) in all ECKey constructors (lines 725, 794, 864), ECDHDecrypter (lines 255, 259), and ECDSAVerifier (line 128).\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.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-04T09:02:00.202619+00:00",
      "status_notes": "Vulnerability CVE-2019-17195 does not affect version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt. CVE-2019-17195 affects Nimbus JOSE+JWT before version 7.9, which fixed multiple uncaught exceptions during JWT parsing that could cause application crashes or authentication bypass. The target version 9.22 is much newer than 7.9 and contains all the fixes. The vulnerability fixes were authored by the upstream maintainer Vladimir Dzhuvinov and were already present in the upstream release before TuxCare began maintaining this version. All exception handling protections are verified in the current codebase: null checks for \"alg\", \"typ\", \"crit\", \"jwk\", \"zip\" parameters, and general exception catching in JSONObjectUtils.parse().\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 Nimbus JOSE+JWT before version 7.9, which fixed multiple uncaught exceptions during JWT parsing that could cause application crashes or authentication bypass. The target version 9.22 is much newer than 7.9 and contains all the fixes. The vulnerability fixes were authored by the upstream maintainer Vladimir Dzhuvinov and were already present in the upstream release before TuxCare began maintaining this version. All exception handling protections are verified in the current codebase: null checks for \"alg\", \"typ\", \"crit\", \"jwk\", \"zip\" parameters, and general exception catching in JSONObjectUtils.parse().\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.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2023-52428 is fixed in version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2023-52428"
      }
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.22-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53864 is fixed in version 9.22-tuxcare.2 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2025-53864"
      }
    }
  ]
}
