{
  "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi",
  "issues" : [
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-1.2-api-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-1.2-api-2.25.3.jar",
      "fingerprint" : "FALLBACK-44bb7cff",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34479: LanguageSpecificPackageVulnerability\u000a\u000aThe Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34479**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-1.2-api|2.25.4|[CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)|\u000a\u000aThe Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\u000a\u000aTwo groups of users are affected:\u000a\u000a  *  Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file.\u000a  *  Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue.\u000a\u000aNote: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the  Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge.\u000a\u000aPackage: org.apache.logging.log4j:log4j-1.2-api\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34479\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1444",
      "severity" : "NORMAL",
      "toString" : "log4j-1.2-api-2.25.3.jar(1,0): CVE-2026-34479: : CVE-2026-34479: LanguageSpecificPackageVulnerability\u000a\u000aThe Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34479**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-1.2-api|2.25.4|[CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)|\u000a\u000aThe Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.\u000a\u000aTwo groups of users are affected:\u000a\u000a  *  Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file.\u000a  *  Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue.\u000a\u000aNote: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the  Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge.\u000a\u000aPackage: org.apache.logging.log4j:log4j-1.2-api\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34479\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34479](https://avd.aquasec.com/nvd/cve-2026-34479)",
      "type" : "CVE-2026-34479"
    }
  ],
  "size" : 1,
  "toString" : "1 warning (normal: 1)"
}