{
  "@id": "urn:uuid:4082362f-dfa8-40e1-8c00-e11aaecbb914",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-10T15:50:03.446715+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.68.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.68.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-08T19:52:29.846723+00:00",
      "status_notes": "Vulnerability CVE-2014-0193 does not affect version 4.1.68.Final-tuxcare.3 of io.netty:netty-all. not_affected \u2014 The target Netty 4.1.68.Final is NOT vulnerable to CVE-2014-0193. The vulnerable code pattern (unbounded text aggregation via fragmentedFramesText/aggregatedText fields) is completely absent from the target. The fix was applied by Norman Maurer (upstream Netty maintainer) on April 30, 2014 in commit 93fab1d5a3, which removed the text aggregation mechanism from WebSocket08FrameDecoder and Contin...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0193"
      },
      "impact_statement": "not_affected \u2014 The target Netty 4.1.68.Final is NOT vulnerable to CVE-2014-0193. The vulnerable code pattern (unbounded text aggregation via fragmentedFramesText/aggregatedText fields) is completely absent from the target. The fix was applied by Norman Maurer (upstream Netty maintainer) on April 30, 2014 in commit 93fab1d5a3, which removed the text aggregation mechanism from WebSocket08FrameDecoder and Contin..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.68.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.68.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-08T19:52:29.846723+00:00",
      "status_notes": "Vulnerability CVE-2019-16869 does not affect version 4.1.68.Final-tuxcare.3 of io.netty:netty-all. CVE-2019-16869 affects Netty before 4.1.42.Final. The target version 4.1.68.Final contains the upstream fix (commit 39cafcb05c) authored by Norman Maurer that properly handles whitespace in HTTP header names per RFC7230#section-3.2.4. The fix rejects HTTP requests with whitespace between header field names and colons (e.g., \"Transfer-Encoding : chunked\") to prevent request smuggling. This fix was already present in the upstream release when TuxCare onboarded version 4.1.68.Final, making the target not affected by this 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": "CVE-2019-16869 affects Netty before 4.1.42.Final. The target version 4.1.68.Final contains the upstream fix (commit 39cafcb05c) authored by Norman Maurer that properly handles whitespace in HTTP header names per RFC7230#section-3.2.4. The fix rejects HTTP requests with whitespace between header field names and colons (e.g., \"Transfer-Encoding : chunked\") to prevent request smuggling. This fix was already present in the upstream release when TuxCare onboarded version 4.1.68.Final, making the target not affected by this 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)."
    }
  ]
}
