{
  "@id": "urn:uuid:a8fb30d0-f7f2-47b6-bd64-2d2125da0ad2",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 16,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-03T12:05:17.011429+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-cli@2.37.0-tuxcare.1",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-cli@2.37.0-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-11-03T12:05:17.011429+00:00",
      "status_notes": "Vulnerability CVE-2023-50780 does not affect version 2.37.0-tuxcare.1 of org.apache.activemq:artemis-cli. Target version 2.37.0-tuxcare.3 is not affected by CVE-2023-50780. The vulnerability (Log4j2 MBean exposure through Jolokia endpoint) was fixed in upstream version 2.29.0 via commits ARTEMIS-4150 and ARTEMIS-4151. The target version already includes these upstream fixes: (1) `-Dlog4j2.disableJmx=true` system property disables Log4j2 MBean registration, and (2) management.xml restricts default MBean access to read-only. The fix commit cfb585eaf61d570eecd65c6ad0e92282df7d3869 by Justin Bertram was already in the upstream 2.37.0 release that TuxCare onboarded, making the vulnerable code pattern absent from this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.29.0), NVD (< 2.29.0), cve.org (< 2.29.0), Snyk (< 2.29.0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2023-50780"
      },
      "impact_statement": "Target version 2.37.0-tuxcare.3 is not affected by CVE-2023-50780. The vulnerability (Log4j2 MBean exposure through Jolokia endpoint) was fixed in upstream version 2.29.0 via commits ARTEMIS-4150 and ARTEMIS-4151. The target version already includes these upstream fixes: (1) `-Dlog4j2.disableJmx=true` system property disables Log4j2 MBean registration, and (2) management.xml restricts default MBean access to read-only. The fix commit cfb585eaf61d570eecd65c6ad0e92282df7d3869 by Justin Bertram was already in the upstream 2.37.0 release that TuxCare onboarded, making the vulnerable code pattern absent from this version.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.29.0), NVD (< 2.29.0), cve.org (< 2.29.0), Snyk (< 2.29.0)."
    }
  ]
}