{
  "@id": "urn:uuid:2f9bfdba-e79f-4cbb-a23e-de1fd0a7be6f",
  "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.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2017-12972 does not affect version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2017-12972: Integer overflow in AAD length computation allowing HMAC bypass. Target version 9.37.3 is NOT AFFECTED. The vulnerable pattern (unchecked byte-to-bit conversion in AAD.computeLength()) is not present. The upstream vendor (Vladimir Dzhuvinov) fixed this vulnerability in version 4.39 (commit 0d2bd649, 2017-06-02) by replacing ByteUtils.bitLength() with ByteUtils.safeBitLength() which validates for integer overflow before HMAC computation. This upstream fix was already included in version 9.37.3 when TuxCare onboarded it. The fix is complete and properly addresses the vulnerability - verified that AAD.computeLength() now throws IntegerOverflowException if aad.length * 8 would overflow an int, preventing the HMAC bypass attack.\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 AAD length computation allowing HMAC bypass. Target version 9.37.3 is NOT AFFECTED. The vulnerable pattern (unchecked byte-to-bit conversion in AAD.computeLength()) is not present. The upstream vendor (Vladimir Dzhuvinov) fixed this vulnerability in version 4.39 (commit 0d2bd649, 2017-06-02) by replacing ByteUtils.bitLength() with ByteUtils.safeBitLength() which validates for integer overflow before HMAC computation. This upstream fix was already included in version 9.37.3 when TuxCare onboarded it. The fix is complete and properly addresses the vulnerability - verified that AAD.computeLength() now throws IntegerOverflowException if aad.length * 8 would overflow an int, preventing the HMAC bypass attack.\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.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T04:43:00.116945+00:00",
      "status_notes": "Vulnerability CVE-2017-12973 does not affect version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. not_affected \u2014 CVE-2017-12973 affects Nimbus JOSE+JWT versions before 4.39. The target version 9.37.3 is significantly newer and already contains the upstream fix (commit 6a29f10f) that prevents padding oracle attacks by validating MAC/HMAC authentication tags BEFORE decryption. The fix was shipped in the upstream release, not added by TuxCare. Both vulnerable methods (decryptAuthenticated and decryptWithConc...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12973"
      },
      "impact_statement": "not_affected \u2014 CVE-2017-12973 affects Nimbus JOSE+JWT versions before 4.39. The target version 9.37.3 is significantly newer and already contains the upstream fix (commit 6a29f10f) that prevents padding oracle attacks by validating MAC/HMAC authentication tags BEFORE decryption. The fix was shipped in the upstream release, not added by TuxCare. Both vulnerable methods (decryptAuthenticated and decryptWithConc..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:04:11.456857+00:00",
      "status_notes": "Vulnerability CVE-2017-12974 does not affect version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2017-12974 (Invalid Curve Attack) is NOT present in target version 9.37.3. The vulnerability was fixed in upstream version 4.36 (April 2017) by commit f3a7a801, authored by Vladimir Dzhuvinov. The fix adds curve validation to ECKey constructors to ensure public coordinates (x, y) satisfy the elliptic curve equation before accepting the key. Version 9.37.3 (December 2023) already contains this fix from upstream, onboarded by TuxCare without modification. All ECKey construction paths (direct x/y coordinates, ECPublicKey extraction, JSON parsing) invoke the validation via ensurePublicCoordinatesOnCurve() which calls ECChecks.isPointOnCurve().\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": "CVE-2017-12974 (Invalid Curve Attack) is NOT present in target version 9.37.3. The vulnerability was fixed in upstream version 4.36 (April 2017) by commit f3a7a801, authored by Vladimir Dzhuvinov. The fix adds curve validation to ECKey constructors to ensure public coordinates (x, y) satisfy the elliptic curve equation before accepting the key. Version 9.37.3 (December 2023) already contains this fix from upstream, onboarded by TuxCare without modification. All ECKey construction paths (direct x/y coordinates, ECPublicKey extraction, JSON parsing) invoke the validation via ensurePublicCoordinatesOnCurve() which calls ECChecks.isPointOnCurve().\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.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2019-17195 does not affect version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2019-17195 affects Nimbus JOSE+JWT before v7.9. The target version 9.37.3 includes the upstream vendor's fix from version 7.9 (October 2019). The fix adds comprehensive exception handling and null checks to prevent uncaught NPE and IllegalArgumentException during JWT/JWS/JWE header parsing. All fix components are verified present in the current code: JSONObjectUtils.parse() catch-all exception handler, Base64URL.from() null-safe constructors, and CommonSEHeader.parsePublicJWK() null checks. The fix was authored by vladimir@dzhuvinov.com (upstream vendor) and shipped in the upstream release that TuxCare onboarded.\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 v7.9. The target version 9.37.3 includes the upstream vendor's fix from version 7.9 (October 2019). The fix adds comprehensive exception handling and null checks to prevent uncaught NPE and IllegalArgumentException during JWT/JWS/JWE header parsing. All fix components are verified present in the current code: JSONObjectUtils.parse() catch-all exception handler, Base64URL.from() null-safe constructors, and CommonSEHeader.parsePublicJWK() null checks. The fix was authored by vladimir@dzhuvinov.com (upstream vendor) and shipped in the upstream release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 7.9), NVD (< 7.9), Snyk (< 7.8.1)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2023-52428 does not affect version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2023-52428: The target repository at version 9.37.3 is NOT AFFECTED. The vulnerability (DoS via unbounded p2c iteration count in PasswordBasedDecrypter) was fixed by upstream vendor Connect2id in version 9.37.2. The fix commit (3b3b77ec) authored by Vladimir Dzhuvinov adds validation that rejects JWE p2c header values exceeding 1,000,000 before performing expensive PBKDF2 operations. This fix was already present in the upstream release when TuxCare onboarded version 9.37.3, so the vulnerable code pattern has never been present in this TuxCare-maintained version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.37.2), NVD (< 9.37.2), Snyk (< 9.37.2).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-52428"
      },
      "impact_statement": "CVE-2023-52428: The target repository at version 9.37.3 is NOT AFFECTED. The vulnerability (DoS via unbounded p2c iteration count in PasswordBasedDecrypter) was fixed by upstream vendor Connect2id in version 9.37.2. The fix commit (3b3b77ec) authored by Vladimir Dzhuvinov adds validation that rejects JWE p2c header values exceeding 1,000,000 before performing expensive PBKDF2 operations. This fix was already present in the upstream release when TuxCare onboarded version 9.37.3, so the vulnerable code pattern has never been present in this TuxCare-maintained version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 9.37.2), NVD (< 9.37.2), Snyk (< 9.37.2)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.37.3-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53864 is fixed in version 9.37.3-tuxcare.1 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2025-53864"
      }
    }
  ]
}
