{
  "@id": "urn:uuid:943bb092-4f13-437f-ab29-709710bb0932",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-12T07:44:19.218908+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-12T07:44:19.218908+00:00",
      "status_notes": "Vulnerability CVE-2015-2156 does not affect version 4.1.48.Final-tuxcare.7 of io.netty:netty-parent. CVE-2015-2156: Target is NOT AFFECTED. The upstream vendor fix (commit 97d871a7 by Stephane Landelle, April 2015) shipped in Netty 4.1.48.Final before TuxCare onboarding. The fix adds RFC6265-compliant character validation for cookie names/values via BitSet-based validators (VALID_COOKIE_NAME_OCTETS, VALID_COOKIE_VALUE_OCTETS) that reject control characters, separators, and other disallowed characters. Decoders (CookieDecoder.initCookie) return null when invalid characters detected in STRICT mode; encoders (CookieEncoder.validateCookie) throw IllegalArgumentException. The defense code exists at codec-http/src/main/java/io/netty/handler/codec/http/cookie/CookieUtil.java:25-149. While LAX mode exists for backward compatibility, STRICT mode provides full RFC6265 protection per vendor design. Fix commit is ancestor of first TuxCare commit (7ccf2196d), confirming upstream origin.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0, < 4.0.28.Final), NVD (<= 3.9.7; = 3.10.0; = 3.10.1; = 3.10.2; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.0.10; = 4.0.11; = 4.0.12; = 4.0.13; = 4.0.14; = 4.0.15; = 4.0.16; = 4.0.17; = 4.0.18; = 4.0.19; = 4.0.20; = 4.0.21; = 4.0.22; = 4.0.23; = 4.0.24; = 4.0.25; = 4.0.26; = 4.0.27; = 4.1.0-beta1; = 4.1.0-beta2; = 4.1.0-beta3; = 4.1.0-beta4), Snyk (>= 4.0.0.Final, < 4.0.28.Final; >= 4.1.0.Beta1, < 4.1.0.Beta5; >= 4.0.0.Final, < 4.0.28.Final; >= 4.1.0.Beta1, < 4.1.0.Beta5).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2015-2156"
      },
      "impact_statement": "CVE-2015-2156: Target is NOT AFFECTED. The upstream vendor fix (commit 97d871a7 by Stephane Landelle, April 2015) shipped in Netty 4.1.48.Final before TuxCare onboarding. The fix adds RFC6265-compliant character validation for cookie names/values via BitSet-based validators (VALID_COOKIE_NAME_OCTETS, VALID_COOKIE_VALUE_OCTETS) that reject control characters, separators, and other disallowed characters. Decoders (CookieDecoder.initCookie) return null when invalid characters detected in STRICT mode; encoders (CookieEncoder.validateCookie) throw IllegalArgumentException. The defense code exists at codec-http/src/main/java/io/netty/handler/codec/http/cookie/CookieUtil.java:25-149. While LAX mode exists for backward compatibility, STRICT mode provides full RFC6265 protection per vendor design. Fix commit is ancestor of first TuxCare commit (7ccf2196d), confirming upstream origin.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 4.0.0, < 4.0.28.Final), NVD (<= 3.9.7; = 3.10.0; = 3.10.1; = 3.10.2; = 4.0.0; = 4.0.1; = 4.0.2; = 4.0.3; = 4.0.4; = 4.0.5; = 4.0.6; = 4.0.7; = 4.0.8; = 4.0.9; = 4.0.10; = 4.0.11; = 4.0.12; = 4.0.13; = 4.0.14; = 4.0.15; = 4.0.16; = 4.0.17; = 4.0.18; = 4.0.19; = 4.0.20; = 4.0.21; = 4.0.22; = 4.0.23; = 4.0.24; = 4.0.25; = 4.0.26; = 4.0.27; = 4.1.0-beta1; = 4.1.0-beta2; = 4.1.0-beta3; = 4.1.0-beta4), Snyk (>= 4.0.0.Final, < 4.0.28.Final; >= 4.1.0.Beta1, < 4.1.0.Beta5; >= 4.0.0.Final, < 4.0.28.Final; >= 4.1.0.Beta1, < 4.1.0.Beta5)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-12T07:44:19.218908+00:00",
      "status_notes": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.48.Final-tuxcare.7 of io.netty:netty-parent.",
      "vulnerability": {
        "name": "GHSA-mfg7-5gfp-c4w3"
      },
      "action_statement": "Vulnerability GHSA-mfg7-5gfp-c4w3 affects version 4.1.48.Final-tuxcare.7 of io.netty:netty-parent."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-parent@4.1.48.Final-tuxcare.7"
          }
        }
      ],
      "timestamp": "2026-11-12T07:44:19.218908+00:00",
      "status_notes": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.48.Final-tuxcare.7 of io.netty:netty-parent.",
      "vulnerability": {
        "name": "GHSA-v74w-7mr3-4qg3"
      },
      "action_statement": "Vulnerability GHSA-v74w-7mr3-4qg3 affects version 4.1.48.Final-tuxcare.7 of io.netty:netty-parent."
    }
  ]
}
