{ "$schema": "http://cyclonedx.org/schema/bom-1.6.schema.json", "bomFormat": "CycloneDX", "specVersion": "1.6", "serialNumber": "urn:uuid:1016bbae-9687-595d-bc08-50fccd8f2aac", "version": 1, "metadata": { "tools": [ { "name": "tuxcare-vex-generator", "version": "1.0.0" } ] }, "components": [ { "bom-ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3", "type": "library", "group": "org.apache.logging.log4j", "name": "log4j-jdbc-dbcp2", "version": "2.22.1-tuxcare.3", "purl": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ], "vulnerabilities": [ { "bom-ref": "urn:uuid:512e2d2b-81b7-5928-8c41-4171853e1d86", "id": "CVE-2014-8180", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2014-8180 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:977cfda9-a827-552d-a8b3-ac617b586f53", "id": "CVE-2016-6494", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2016-6494 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:aed87dba-79b1-5a8a-9cc4-0d47ac4f5abd", "id": "CVE-2021-32036", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-32036 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:e08388c2-f7d5-5206-a01b-40394f138df5", "id": "CVE-2021-38295", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2021-38295 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:293a960a-b932-5e54-88aa-8275bb2e635d", "id": "CVE-2022-24706", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2022-24706 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:8c595516-76d0-51e9-b1cb-d20de0ff7535", "id": "CVE-2023-26268", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-26268 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:dabcefb7-62dd-5b0d-8016-02d899207fbe", "id": "CVE-2023-45725", "analysis": { "state": "false_positive", "detail": "Vulnerability CVE-2023-45725 is a false positive for org.apache.logging.log4j:log4j-jdbc-dbcp2 2.22.1-tuxcare.3." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:1eb61f63-30f7-5c6d-a98d-9a015c9ed47a", "id": "CVE-2025-68161", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2025-68161 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:25e5287e-9e79-51b8-9185-ec002610a0c4", "id": "CVE-2026-34477", "analysis": { "state": "exploitable", "detail": "Vulnerability CVE-2026-34477 affects version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:27ce1fd6-9d5e-5303-9960-aa79d32bd984", "id": "CVE-2026-34478", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-34478 does not affect version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2. Version not vulnerable (per prereq analysis); terminalized." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:20603d3d-7317-5a7b-bcac-bc646dd17cd3", "id": "CVE-2026-34479", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-34479 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:cbea7bd9-0371-5665-b4e6-f8112d0dfae7", "id": "CVE-2026-34480", "analysis": { "state": "not_affected", "detail": "Vulnerability CVE-2026-34480 does not affect version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2. Version 2.22.1 is not vulnerable. Summary: The target repository version 2.22.1-tuxcare.1 is NOT VULNERABLE to CVE-2026-34480. While the XmlLayout feature exists, the sanitization fix that addresses the vulnerability has been backported and is fully implemented in the current codebase. [terminalized not_affected from patch_application_manual/not_vulnerable]" }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:029a17ee-bff7-5de7-89f4-fca6e2bfc65a", "id": "CVE-2026-34481", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-34481 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }, { "bom-ref": "urn:uuid:697111ee-ea0d-559c-ba7a-1a63ffac593f", "id": "CVE-2026-49844", "analysis": { "state": "resolved", "detail": "Vulnerability CVE-2026-49844 is fixed in version 2.22.1-tuxcare.3 of org.apache.logging.log4j:log4j-jdbc-dbcp2." }, "affects": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] } ], "dependencies": [ { "ref": "pkg:maven/org.apache.logging.log4j/log4j-jdbc-dbcp2@2.22.1-tuxcare.3" } ] }