{
  "@id": "urn:uuid:696cef87-3c24-4d7a-9b05-76dda88bcf5a",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 20,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T14:09:00.038715+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.87.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.87.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-01T15:25:00.106741+00:00",
      "status_notes": "Vulnerability CVE-2014-0193 does not affect version 4.1.87.Final-tuxcare.3 of io.netty:netty-all. not_affected \u2014 CVE-2014-0193 is not present in Netty 4.1.87.Final-tuxcare.3. The vulnerability (unbounded memory allocation via text accumulation in StringBuilder during fragmented WebSocket frame processing) was fixed by upstream commit 93fab1d5a3 authored by Norman Maurer, which shipped in the upstream Netty 4.1.87.Final release that TuxCare onboarded. The target uses Utf8Validator (validation-only) instead...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0193"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-0193 is not present in Netty 4.1.87.Final-tuxcare.3. The vulnerability (unbounded memory allocation via text accumulation in StringBuilder during fragmented WebSocket frame processing) was fixed by upstream commit 93fab1d5a3 authored by Norman Maurer, which shipped in the upstream Netty 4.1.87.Final release that TuxCare onboarded. The target uses Utf8Validator (validation-only) instead..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.87.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.87.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-03T12:15:19.421943+00:00",
      "status_notes": "Vulnerability CVE-2019-16869 does not affect version 4.1.87.Final-tuxcare.3 of io.netty:netty-all. The target Netty 4.1.87.Final already contains the upstream fix for CVE-2019-16869. The vulnerability was fixed in upstream Netty 4.1.42.Final (commit 39cafcb05c by Norman Maurer on 2019-09-20). The fix properly handles whitespace before colons in HTTP headers per RFC 7230 section 3.2.4: for requests, whitespace before the colon is not stripped, causing header validation to fail and preventing request smuggling; for responses, whitespace is stripped for compatibility. The fix was present in the upstream 4.1.87.Final release that TuxCare onboarded, so this version is not affected by the vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0.Beta1, < 4.1.42.Final), NVD (< 4.1.42), Snyk (< 4.1.42.Final; < 4.1.42.Final).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-16869"
      },
      "impact_statement": "The target Netty 4.1.87.Final already contains the upstream fix for CVE-2019-16869. The vulnerability was fixed in upstream Netty 4.1.42.Final (commit 39cafcb05c by Norman Maurer on 2019-09-20). The fix properly handles whitespace before colons in HTTP headers per RFC 7230 section 3.2.4: for requests, whitespace before the colon is not stripped, causing header validation to fail and preventing request smuggling; for responses, whitespace is stripped for compatibility. The fix was present in the upstream 4.1.87.Final release that TuxCare onboarded, so this version is not affected by the vulnerability.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0.Beta1, < 4.1.42.Final), NVD (< 4.1.42), Snyk (< 4.1.42.Final; < 4.1.42.Final)."
    }
  ]
}
