{
  "@id": "urn:uuid:f1df52d6-a9bd-46a3-b9e0-c1d223e06d65",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-14T02:54:11.763221+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2014-3488 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. not_affected \u2014 CVE-2014-3488 affects Netty before 3.9.2, where SSLv2Hello messages caused infinite loops due to BUFFER_OVERFLOW handling that never allocated sufficiently large buffers. The target (Netty 4.1.124.Final) has proper BUFFER_OVERFLOW handling at SslHandler.java:1526-1537 that allocates a new buffer sized to engine.getSession().getApplicationBufferSize() and retries, preventing infinite loops. This...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-3488"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-3488 affects Netty before 3.9.2, where SSLv2Hello messages caused infinite loops due to BUFFER_OVERFLOW handling that never allocated sufficiently large buffers. The target (Netty 4.1.124.Final) has proper BUFFER_OVERFLOW handling at SslHandler.java:1526-1537 that allocates a new buffer sized to engine.getSession().getApplicationBufferSize() and retries, preventing infinite loops. This..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2016-4970 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. The target Netty 4.1.124.Final is NOT vulnerable to CVE-2016-4970. The fix for the infinite loop vulnerability was shipped in upstream Netty 4.1.1.Final (May 2016) and is present in the target code. The vulnerable pattern (infinite loop when SSL_write returns WANT_READ/WANT_WRITE with no BIO data) has been eliminated by proper error handling that returns control to the caller instead of continuing the loop.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0.Alpha1, < 4.0.37.Final; >= 4.1.0.Beta1, < 4.1.1.Final), NVD (>= 4.0.20, < 4.0.37; >= 4.1.0, < 4.1.1), Snyk (>= 4.0.0.Alpha1, < 4.0.37.Final; >= 4.1.0.Beta1, < 4.1.1.Final).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2016-4970"
      },
      "impact_statement": "The target Netty 4.1.124.Final is NOT vulnerable to CVE-2016-4970. The fix for the infinite loop vulnerability was shipped in upstream Netty 4.1.1.Final (May 2016) and is present in the target code. The vulnerable pattern (infinite loop when SSL_write returns WANT_READ/WANT_WRITE with no BIO data) has been eliminated by proper error handling that returns control to the caller instead of continuing the loop.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0.Alpha1, < 4.0.37.Final; >= 4.1.0.Beta1, < 4.1.1.Final), NVD (>= 4.0.20, < 4.0.37; >= 4.1.0, < 4.1.1), Snyk (>= 4.0.0.Alpha1, < 4.0.37.Final; >= 4.1.0.Beta1, < 4.1.1.Final)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2019-20445 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. The upstream fix was released in 4.1.45, and version 4.1.124.Final is a later release of the same line. Advisories: GitHub GHSA-p2v9-g2qv-p635 (fixed in 4.1.45), NVD (fixed in 4.1.44).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-20445"
      },
      "impact_statement": "Prechecker: An upstream release that contains the fix is part of this version's source history, and the code the fix removes is gone. The upstream fix was released in 4.1.45, and version 4.1.124.Final is a later release of the same line. Advisories: GitHub GHSA-p2v9-g2qv-p635 (fixed in 4.1.45), NVD (fixed in 4.1.44)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2020-11612 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. CVE-2020-11612 affects Netty 4.1.x before 4.1.46. The target is Netty 4.1.124.Final, which includes the upstream fix (commit 1543218d3e) that adds maxAllocation limits to ZlibDecoder classes. The vulnerable pattern (unbounded decompression buffer allocation) is not present because the fix was already shipped in the upstream release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.0, < 4.1.46), NVD (>= 4.1, < 4.1.46), Snyk (>= 4.1.0.Final, < 4.1.46.Final).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-11612"
      },
      "impact_statement": "CVE-2020-11612 affects Netty 4.1.x before 4.1.46. The target is Netty 4.1.124.Final, which includes the upstream fix (commit 1543218d3e) that adds maxAllocation limits to ZlibDecoder classes. The vulnerable pattern (unbounded decompression buffer allocation) is not present because the fix was already shipped in the upstream release that TuxCare onboarded.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.0, < 4.1.46), NVD (>= 4.1, < 4.1.46), Snyk (>= 4.1.0.Final, < 4.1.46.Final)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2020-7238 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. The target Netty 4.1.124.Final is not affected by CVE-2020-7238. The upstream fix commit 8494b046ec from 2019-12-13 is already present in the release. This fix was first included in Netty 4.1.44.Final, and the target version is much newer. The vulnerable code patterns (accepting multiple Content-Length headers or both Content-Length and Transfer-Encoding without validation) are not present. Additionally, default header name validation rejects headers with leading whitespace, blocking the specific attack vector mentioned in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.43, < 4.1.45), NVD (= 4.1.43), Snyk (< 4.1.44.Final; < 4.1.44.Final).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2020-7238"
      },
      "impact_statement": "The target Netty 4.1.124.Final is not affected by CVE-2020-7238. The upstream fix commit 8494b046ec from 2019-12-13 is already present in the release. This fix was first included in Netty 4.1.44.Final, and the target version is much newer. The vulnerable code patterns (accepting multiple Content-Length headers or both Content-Length and Transfer-Encoding without validation) are not present. Additionally, default header name validation rejects headers with leading whitespace, blocking the specific attack vector mentioned in the CVE.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.43, < 4.1.45), NVD (= 4.1.43), Snyk (< 4.1.44.Final; < 4.1.44.Final)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2023-34462 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. not_affected \u2014 CVE-2023-34462 is NOT present in Netty 4.1.124.Final. The vulnerability (unbounded buffer allocation based on attacker-controlled ClientHello length, allowing up to 16MB per connection leading to memory exhaustion DoS) was fixed in upstream commit 535da17e45 (June 2023) which added maxClientHelloLength validation. This fix was already included in the upstream Netty 4.1.124.Final release before ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-34462"
      },
      "impact_statement": "not_affected \u2014 CVE-2023-34462 is NOT present in Netty 4.1.124.Final. The vulnerability (unbounded buffer allocation based on attacker-controlled ClientHello length, allowing up to 16MB per connection leading to memory exhaustion DoS) was fixed in upstream commit 535da17e45 (June 2023) which added maxClientHelloLength validation. This fix was already included in the upstream Netty 4.1.124.Final release before ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2023-4586 is a false positive for io.netty:netty-handler 4.1.124.Final-tuxcare.1.",
      "vulnerability": {
        "name": "CVE-2023-4586"
      },
      "impact_statement": "The vulnerability has been withdrawn."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2025-24970 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler. The target Netty 4.1.124.Final is not affected by CVE-2025-24970. The vulnerability involves improper validation of SSL/TLS packets with insufficient data, leading to potential native crashes. The upstream fix (commit 87f40725155b2f89adfde68c7732f97c153676c4 by Norman Maurer) was committed on 2025-02-10 and was already included in the upstream 4.1.124.Final release (tagged 2025-08-13) before TuxCare onboarded this version on 2026-10-15. The fix adds early length validation checks in SslUtils.getEncryptedPacketLength() to ensure sufficient data is present before parsing SSL packet structure, adds an assert to verify packetLength is non-negative, and corrects the return value for invalid SSLv2 packets. All fix components are present and active in the target code at HEAD.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.91.Final, < 4.1.118.Final), NVD (>= 4.1.91, < 4.1.118), cve.org (>= 4.1.91.Final, <= 4.1.117.Final), Snyk (>= 4.1.91.Final, < 4.1.118.Final; >= 4.2.0.Alpha1, < 4.2.0.RC3).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2025-24970"
      },
      "impact_statement": "The target Netty 4.1.124.Final is not affected by CVE-2025-24970. The vulnerability involves improper validation of SSL/TLS packets with insufficient data, leading to potential native crashes. The upstream fix (commit 87f40725155b2f89adfde68c7732f97c153676c4 by Norman Maurer) was committed on 2025-02-10 and was already included in the upstream 4.1.124.Final release (tagged 2025-08-13) before TuxCare onboarded this version on 2026-10-15. The fix adds early length validation checks in SslUtils.getEncryptedPacketLength() to ensure sufficient data is present before parsing SSL packet structure, adds an assert to verify packetLength is non-negative, and corrects the return value for invalid SSLv2 packets. All fix components are present and active in the target code at HEAD.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.1.91.Final, < 4.1.118.Final), NVD (>= 4.1.91, < 4.1.118), cve.org (>= 4.1.91.Final, <= 4.1.117.Final), Snyk (>= 4.1.91.Final, < 4.1.118.Final; >= 4.2.0.Alpha1, < 4.2.0.RC3)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2026-44249 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler.",
      "vulnerability": {
        "name": "CVE-2026-44249"
      },
      "action_statement": "Vulnerability CVE-2026-44249 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2026-45416 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler.",
      "vulnerability": {
        "name": "CVE-2026-45416"
      },
      "action_statement": "Vulnerability CVE-2026-45416 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2026-50010 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler.",
      "vulnerability": {
        "name": "CVE-2026-50010"
      },
      "action_statement": "Vulnerability CVE-2026-50010 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2026-75595 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler.",
      "vulnerability": {
        "name": "CVE-2026-75595"
      },
      "action_statement": "Vulnerability CVE-2026-75595 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-handler@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2026-75596 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler.",
      "vulnerability": {
        "name": "CVE-2026-75596"
      },
      "action_statement": "Vulnerability CVE-2026-75596 affects version 4.1.124.Final-tuxcare.1 of io.netty:netty-handler."
    }
  ]
}
