{
  "@id": "urn:uuid:65cbe93b-f41c-493d-b226-35b71e789770",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-13T20:33:15.400563+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.netty/netty-parent@4.1.46.Final-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/io.netty/netty-parent@4.1.46.Final-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-13T20:33:15.400563+00:00",
      "status_notes": "Vulnerability CVE-2015-2156 does not affect version 4.1.46.Final-tuxcare.2 of io.netty:netty-parent. CVE-2015-2156 is not present in Netty 4.1.46.Final. The vulnerability affects versions before 4.1.0.Beta5, and the fix was included in the upstream 4.1.0.Beta5 release in 2015. The target version 4.1.46.Final already contains the upstream fix commit 97d871a755 which adds RFC6265-compliant character validation for cookie names and values. The fix includes validation BitSets and enforcement in both CookieEncoder (throws exceptions) and CookieDecoder (discards invalid cookies).\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 is not present in Netty 4.1.46.Final. The vulnerability affects versions before 4.1.0.Beta5, and the fix was included in the upstream 4.1.0.Beta5 release in 2015. The target version 4.1.46.Final already contains the upstream fix commit 97d871a755 which adds RFC6265-compliant character validation for cookie names and values. The fix includes validation BitSets and enforcement in both CookieEncoder (throws exceptions) and CookieDecoder (discards invalid cookies).\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)."
    }
  ]
}
