{
  "@id": "urn:uuid:4f74cadf-d350-4694-af48-6676a9fd1809",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-12T09:13:20.704692+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.74.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.74.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:13:20.704692+00:00",
      "status_notes": "Vulnerability CVE-2014-0193 does not affect version 4.1.74.Final-tuxcare.3 of io.netty:netty-all. not_affected \u2014 CVE-2014-0193 affects Netty versions before 4.0.19 due to unbounded memory accumulation in WebSocket08FrameDecoder. The target (Netty 4.1.74.Final) is not affected because the upstream fix was already present in the 4.1.74.Final release. The vulnerable pattern (fragmentedFramesText field storing all fragmented frame text in a StringBuilder) does not exist in the target code. The fix (commit 93f...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0193"
      },
      "impact_statement": "not_affected \u2014 CVE-2014-0193 affects Netty versions before 4.0.19 due to unbounded memory accumulation in WebSocket08FrameDecoder. The target (Netty 4.1.74.Final) is not affected because the upstream fix was already present in the 4.1.74.Final release. The vulnerable pattern (fragmentedFramesText field storing all fragmented frame text in a StringBuilder) does not exist in the target code. The fix (commit 93f..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.74.Final-tuxcare.3",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.74.Final-tuxcare.3"
          }
        }
      ],
      "timestamp": "2026-11-12T09:13:20.704692+00:00",
      "status_notes": "Vulnerability CVE-2019-16869 does not affect version 4.1.74.Final-tuxcare.3 of io.netty:netty-all. CVE-2019-16869 affects Netty before 4.1.42.Final. The target repository is at version 4.1.74.Final (32 releases later), which already contains the upstream fix. The vulnerability allowed HTTP request smuggling via whitespace before the colon in HTTP headers (e.g., \"Transfer-Encoding : chunked\"). The fix (commit 39cafcb05c by Norman Maurer, Sept 2019) is present in HttpObjectDecoder.java lines 879-884, implementing RFC 7230's requirement to reject such malformed headers in requests while maintaining backward compatibility for responses. The fix was included in the upstream 4.1.42.Final release that TuxCare later onboarded, making this an upstream-provided fix rather than a TuxCare backport.\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 repository is at version 4.1.74.Final (32 releases later), which already contains the upstream fix. The vulnerability allowed HTTP request smuggling via whitespace before the colon in HTTP headers (e.g., \"Transfer-Encoding : chunked\"). The fix (commit 39cafcb05c by Norman Maurer, Sept 2019) is present in HttpObjectDecoder.java lines 879-884, implementing RFC 7230's requirement to reject such malformed headers in requests while maintaining backward compatibility for responses. The fix was included in the upstream 4.1.42.Final release that TuxCare later onboarded, making this an upstream-provided fix rather than a TuxCare backport.\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)."
    }
  ]
}
