{
  "@id": "urn:uuid:6eade251-7f43-45ba-8dc4-8048d3d3ab3b",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-07T00:41:35.685763+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-07T00:41:35.685763+00:00",
      "status_notes": "Vulnerability CVE-2012-5575 does not affect version 3.4.5-tuxcare.2 of org.apache.cxf:cxf-rt-transports-http. not_affected \u2014 Apache CXF 3.4.5 is not affected by CVE-2012-5575. The vulnerability, which allowed attackers to force CXF to use weaker cryptographic algorithms by not verifying algorithms before decryption, was fixed in upstream Apache CXF version 2.7.4 (February 2013). The fix adds setAlgorithmSuites() method that translates WS-SecurityPolicy AlgorithmSuite definitions into WSS4J AlgorithmSuite objects and ...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2012-5575"
      },
      "impact_statement": "not_affected \u2014 Apache CXF 3.4.5 is not affected by CVE-2012-5575. The vulnerability, which allowed attackers to force CXF to use weaker cryptographic algorithms by not verifying algorithms before decryption, was fixed in upstream Apache CXF version 2.7.4 (February 2013). The fix adds setAlgorithmSuites() method that translates WS-SecurityPolicy AlgorithmSuite definitions into WSS4J AlgorithmSuite objects and ..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-07T00:41:35.685763+00:00",
      "status_notes": "Vulnerability CVE-2018-8039 does not affect version 3.4.5-tuxcare.2 of org.apache.cxf:cxf-rt-transports-http. The target Apache CXF 3.4.5 is NOT AFFECTED by CVE-2018-8039. The vulnerability involved hostname verification being silently bypassed when using the deprecated com.sun.net.ssl stack due to reflection exception handling that returned 'true' (verification passed) instead of 'false' (verification failed). The upstream fix commit fae6fabf9bd7647f5e9cb68897a7d72b545b741b from May 2018 corrected this by changing the exception handler to return 'false', properly rejecting connections when hostname verification fails. This fix was already present in the upstream Apache CXF 3.4.5 release that TuxCare onboarded, as confirmed by git ancestry analysis showing the fix commit predates the first TuxCare commit (b4e3552acd2 \"Onboarding for 3.4.5\"). The fix is verified in the current code at HttpsURLConnectionFactory.java line 193.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 3.2.0, < 3.2.5; < 3.1.16; >= 3.2.0, < 3.2.5; < 3.1.16), NVD (< 3.1.16; >= 3.2.0, < 3.2.5), cve.org (< 3.1.16; >= 3.2, < 3.2.5), Snyk (< 3.1.16; >= 3.2.0, < 3.2.6).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2018-8039"
      },
      "impact_statement": "The target Apache CXF 3.4.5 is NOT AFFECTED by CVE-2018-8039. The vulnerability involved hostname verification being silently bypassed when using the deprecated com.sun.net.ssl stack due to reflection exception handling that returned 'true' (verification passed) instead of 'false' (verification failed). The upstream fix commit fae6fabf9bd7647f5e9cb68897a7d72b545b741b from May 2018 corrected this by changing the exception handler to return 'false', properly rejecting connections when hostname verification fails. This fix was already present in the upstream Apache CXF 3.4.5 release that TuxCare onboarded, as confirmed by git ancestry analysis showing the fix commit predates the first TuxCare commit (b4e3552acd2 \"Onboarding for 3.4.5\"). The fix is verified in the current code at HttpsURLConnectionFactory.java line 193.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (>= 3.2.0, < 3.2.5; < 3.1.16; >= 3.2.0, < 3.2.5; < 3.1.16), NVD (< 3.1.16; >= 3.2.0, < 3.2.5), cve.org (< 3.1.16; >= 3.2, < 3.2.5), Snyk (< 3.1.16; >= 3.2.0, < 3.2.6)."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2",
          "identifiers": {
            "purl": "pkg:maven/org.apache.cxf/cxf-rt-transports-http@3.4.5-tuxcare.2"
          }
        }
      ],
      "timestamp": "2026-11-07T00:41:35.685763+00:00",
      "status_notes": "Vulnerability CVE-2024-41172 does not affect version 3.4.5-tuxcare.2 of org.apache.cxf:cxf-rt-transports-http. not_affected \u2014 Apache CXF 3.4.5 is NOT affected by CVE-2024-41172. The CVE explicitly states \"3.5.x and lower versions are not impacted\" - this vulnerability was a regression introduced in versions 3.6.0-3.6.3 and 4.0.0-4.0.4. The target version (3.4.5) uses a safe shared-client architecture where a single CloseableHttpAsyncClient instance is created per AsyncHTTPConduitFactory and shared across multiple cond...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2024-41172"
      },
      "impact_statement": "not_affected \u2014 Apache CXF 3.4.5 is NOT affected by CVE-2024-41172. The CVE explicitly states \"3.5.x and lower versions are not impacted\" - this vulnerability was a regression introduced in versions 3.6.0-3.6.3 and 4.0.0-4.0.4. The target version (3.4.5) uses a safe shared-client architecture where a single CloseableHttpAsyncClient instance is created per AsyncHTTPConduitFactory and shared across multiple cond..."
    }
  ]
}
