{
  "@id": "urn:uuid:6130c894-a21b-430f-8518-a6f2eb10d8bb",
  "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-all@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2014-0193 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-all. not_affected \u2014 Target Netty 4.1.124.Final is not affected by CVE-2014-0193. The vulnerable pattern (unbounded memory accumulation in WebSocket frame decoder) is not present. The fix was applied by upstream Netty maintainer Norman Maurer in commit 93fab1d5 (shipped in 4.1.0.Beta1, long before 4.1.124.Final). TuxCare's onboarding simply imported the already-fixed upstream release.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2014-0193"
      },
      "impact_statement": "not_affected \u2014 Target Netty 4.1.124.Final is not affected by CVE-2014-0193. The vulnerable pattern (unbounded memory accumulation in WebSocket frame decoder) is not present. The fix was applied by upstream Netty maintainer Norman Maurer in commit 93fab1d5 (shipped in 4.1.0.Beta1, long before 4.1.124.Final). TuxCare's onboarding simply imported the already-fixed upstream release."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-all@4.1.124.Final-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-all@4.1.124.Final-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-14T02:54:11.763221+00:00",
      "status_notes": "Vulnerability CVE-2019-16869 does not affect version 4.1.124.Final-tuxcare.1 of io.netty:netty-all. The target (Netty 4.1.124.Final) is not affected by CVE-2019-16869. The vulnerability was fixed in upstream Netty 4.1.42.Final (September 2019) by commit 39cafcb05c (author: Norman Maurer). TuxCare onboarded version 4.1.124.Final, which already contained the upstream fix. The vulnerable code pattern (whitespace before colon in HTTP headers being stripped during parsing, enabling request smuggling) is not present in the target. The fix modifies HttpObjectDecoder.splitHeader() to prevent whitespace stripping for requests, causing DefaultHttpHeaders validation to reject malformed headers with IllegalArgumentException.\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.124.Final) is not affected by CVE-2019-16869. The vulnerability was fixed in upstream Netty 4.1.42.Final (September 2019) by commit 39cafcb05c (author: Norman Maurer). TuxCare onboarded version 4.1.124.Final, which already contained the upstream fix. The vulnerable code pattern (whitespace before colon in HTTP headers being stripped during parsing, enabling request smuggling) is not present in the target. The fix modifies HttpObjectDecoder.splitHeader() to prevent whitespace stripping for requests, causing DefaultHttpHeaders validation to reject malformed headers with IllegalArgumentException.\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)."
    }
  ]
}
