{
  "@id": "urn:uuid:691f0e8f-06be-4c48-99ff-0f1acab358c0",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 5,
  "@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.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:10:25.284357+00:00",
      "status_notes": "Vulnerability CVE-2017-12972 does not affect version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. Target version 9.23 is not affected by CVE-2017-12972. The vulnerability (integer overflow in byte-to-bit conversion for AAD length computation, enabling HMAC bypass) was fixed in upstream commit 0d2bd649 by Vladimir Dzhuvinov on 2017-06-01. This fix introduced IntegerOverflowException and safeBitLength() methods that prevent integer overflow when converting byte lengths to bit lengths. The fix shipped in the upstream release 9.23 before TuxCare onboarded the project (onboarding commit 08afcde3 by evasilev@cloudlinux.com). All critical HMAC computation paths in AESCBC.encryptAuthenticated and AESCBC.decryptAuthenticated call AAD.computeLength, which uses the safe overflow-checked method.\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": "Target version 9.23 is not affected by CVE-2017-12972. The vulnerability (integer overflow in byte-to-bit conversion for AAD length computation, enabling HMAC bypass) was fixed in upstream commit 0d2bd649 by Vladimir Dzhuvinov on 2017-06-01. This fix introduced IntegerOverflowException and safeBitLength() methods that prevent integer overflow when converting byte lengths to bit lengths. The fix shipped in the upstream release 9.23 before TuxCare onboarded the project (onboarding commit 08afcde3 by evasilev@cloudlinux.com). All critical HMAC computation paths in AESCBC.encryptAuthenticated and AESCBC.decryptAuthenticated call AAD.computeLength, which uses the safe overflow-checked method.\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.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T04:42:00.171839+00:00",
      "status_notes": "Vulnerability CVE-2017-12973 does not affect version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. not_affected \u2014 Target version 9.23 is not affected by CVE-2017-12973. The vulnerability (padding oracle attack due to decrypting before HMAC validation) was fixed in upstream commit 6a29f10f (June 2017) by Vladimir Dzhuvinov, which is present in the upstream release 9.23 that TuxCare onboarded. The vulnerable code pattern (decrypt-then-check) has been replaced with the correct pattern (check-HMAC-first-then-d...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2017-12973"
      },
      "impact_statement": "not_affected \u2014 Target version 9.23 is not affected by CVE-2017-12973. The vulnerability (padding oracle attack due to decrypting before HMAC validation) was fixed in upstream commit 6a29f10f (June 2017) by Vladimir Dzhuvinov, which is present in the upstream release 9.23 that TuxCare onboarded. The vulnerable code pattern (decrypt-then-check) has been replaced with the correct pattern (check-HMAC-first-then-d..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2017-12974 does not affect version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2017-12974 is NOT present in the target. The vulnerability affects Nimbus JOSE+JWT versions before 4.36, which failed to validate that EC public key x,y coordinates are on the specified curve, enabling Invalid Curve Attacks. The target is version 9.23-tuxcare.1, which includes the upstream fix from version 4.36 (2017-04-13). The fix validates coordinates at ECKey construction time using ECChecks.isPointOnCurve(), which verifies the elliptic curve equation (y\u00b2 = x\u00b3 + ax + b mod p). All six ECKey constructors, ECDSAVerifier, and ECDHDecrypter include this validation. The fix was authored by upstream vendor Vladimir Dzhuvinov and shipped in the upstream release that TuxCare onboarded.\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 is NOT present in the target. The vulnerability affects Nimbus JOSE+JWT versions before 4.36, which failed to validate that EC public key x,y coordinates are on the specified curve, enabling Invalid Curve Attacks. The target is version 9.23-tuxcare.1, which includes the upstream fix from version 4.36 (2017-04-13). The fix validates coordinates at ECKey construction time using ECChecks.isPointOnCurve(), which verifies the elliptic curve equation (y\u00b2 = x\u00b3 + ax + b mod p). All six ECKey constructors, ECDSAVerifier, and ECDHDecrypter include this validation. The fix was authored by upstream vendor Vladimir Dzhuvinov and shipped in the upstream release that TuxCare onboarded.\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.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:03:00.104314+00:00",
      "status_notes": "Vulnerability CVE-2019-17195 does not affect version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. CVE-2019-17195 affects Nimbus JOSE+JWT versions before 7.9. The target version 9.23-tuxcare.1 is much newer and contains all upstream fixes from version 7.9 (released October 2019). The fixes address multiple uncaught exception issues during JWT parsing by adding null checks and exception handling. All protective code is present in the current version, having been 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 versions before 7.9. The target version 9.23-tuxcare.1 is much newer and contains all upstream fixes from version 7.9 (released October 2019). The fixes address multiple uncaught exception issues during JWT parsing by adding null checks and exception handling. All protective code is present in the current version, having been 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": "fixed",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2023-52428 is fixed in version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt.",
      "vulnerability": {
        "name": "CVE-2023-52428"
      }
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/com.nimbusds/nimbus-jose-jwt@9.23-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-24T09:31:26.931840+00:00",
      "status_notes": "Vulnerability CVE-2025-53864 does not affect version 9.23-tuxcare.1 of com.nimbusds:nimbus-jose-jwt. already_fixed \u2014 Target repository version 9.23 contains a StackOverflowError catch in JSONObjectUtils.parse() that prevents DoS from deeply nested JSON in JWT claim sets. This defense was added in version 9.10.1 (June 2021), years before CVE-2025-53864 was published. While the target uses a different JSON library (net.minidev json-smart 2.4.8) than the upstream fix (Gson), it implements the same defensive mech...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-53864"
      },
      "impact_statement": "already_fixed \u2014 Target repository version 9.23 contains a StackOverflowError catch in JSONObjectUtils.parse() that prevents DoS from deeply nested JSON in JWT claim sets. This defense was added in version 9.10.1 (June 2021), years before CVE-2025-53864 was published. While the target uses a different JSON library (net.minidev json-smart 2.4.8) than the upstream fix (Gson), it implements the same defensive mech..."
    }
  ]
}
