{
  "@id": "urn:uuid:b3af25c4-5525-4045-8a13-5dd436c4bf60",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 5,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-04T09:05:53.304095+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/io.projectreactor.netty/reactor-netty@1.0.18-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.projectreactor.netty/reactor-netty@1.0.18-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-04T09:05:53.304095+00:00",
      "status_notes": "Vulnerability CVE-2019-11284 does not affect version 1.0.18-tuxcare.1 of io.projectreactor.netty:reactor-netty. Target reactor-netty 1.0.18-tuxcare.1 is NOT AFFECTED by CVE-2019-11284. The vulnerability (passing authorization headers through HTTP redirects to different servers) was fixed in upstream commit fbce9325c (July 2020) by Violeta Georgieva (violetag@vmware.com), which was already present in the upstream release 1.0.18 that TuxCare onboarded in October 2026. The fix introduces a `fromURI` field to track redirect source and compares it against the redirect target (`toURI`) using address comparison. When they differ, or when downgrading from HTTPS to HTTP, sensitive headers (Authorization, Cookie, Proxy-Authorization, Expect) are stripped before the follow-up request is sent. This prevents credential leakage to unintended servers.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 0.8.11), NVD (>= 0.8.0, < 0.8.11), cve.org (< 0.8.11.RELEASE), Snyk (>= 0.8.0, < 0.8.11.RELEASE).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2019-11284"
      },
      "impact_statement": "Target reactor-netty 1.0.18-tuxcare.1 is NOT AFFECTED by CVE-2019-11284. The vulnerability (passing authorization headers through HTTP redirects to different servers) was fixed in upstream commit fbce9325c (July 2020) by Violeta Georgieva (violetag@vmware.com), which was already present in the upstream release 1.0.18 that TuxCare onboarded in October 2026. The fix introduces a `fromURI` field to track redirect source and compares it against the redirect target (`toURI`) using address comparison. When they differ, or when downgrading from HTTPS to HTTP, sensitive headers (Authorization, Cookie, Proxy-Authorization, Expect) are stripped before the follow-up request is sent. This prevents credential leakage to unintended servers.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 0.8.11), NVD (>= 0.8.0, < 0.8.11), cve.org (< 0.8.11.RELEASE), Snyk (>= 0.8.0, < 0.8.11.RELEASE)."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/io.projectreactor.netty/reactor-netty@1.0.18-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/io.projectreactor.netty/reactor-netty@1.0.18-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-02T12:33:00.444385+00:00",
      "status_notes": "Vulnerability CVE-2026-41715 is fixed in version 1.0.18-tuxcare.1 of io.projectreactor.netty:reactor-netty.",
      "vulnerability": {
        "name": "CVE-2026-41715"
      }
    }
  ]
}
