{
  "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi",
  "issues" : [
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-layout-template-json-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayMonitor.war/WEB-INF/lib/log4j-layout-template-json-2.25.3.jar",
      "fingerprint" : "FALLBACK-78a9f3ba",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's  JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a  *  The application uses JsonTemplateLayout.\u000a  *  The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1398",
      "severity" : "NORMAL",
      "toString" : "log4j-layout-template-json-2.25.3.jar(1,0): CVE-2026-34481: : CVE-2026-34481: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34481**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-layout-template-json|2.25.4, 3.0.0-beta3|[CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)|\u000a\u000aApache Log4j's  JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.\u000a\u000aAn attacker can exploit this issue only if both of the following conditions are met:\u000a\u000a  *  The application uses JsonTemplateLayout.\u000a  *  The application logs a MapMessage containing an attacker-controlled floating-point value.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-layout-template-json\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34481\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4, 3.0.0-beta3\u000aLink: [CVE-2026-34481](https://avd.aquasec.com/nvd/cve-2026-34481)",
      "type" : "CVE-2026-34481"
    }
  ],
  "size" : 1,
  "toString" : "1 warning (normal: 1)"
}