{
  "_class" : "io.jenkins.plugins.analysis.core.restapi.ReportApi",
  "issues" : [
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-core-2.25.3.jar",
      "fingerprint" : "FALLBACK-6362715e",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34477: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34477**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34477](https://avd.aquasec.com/nvd/cve-2026-34477)|\u000a\u000aThe fix for  CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161  was incomplete: it addressed hostname verification only when enabled via the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property, but not when configured through the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  attribute of the <Ssl> element.\u000a\u000aAlthough the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.\u000a\u000aA network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:\u000a\u000a  *  An SMTP, Socket, or Syslog appender is in use.\u000a  *  TLS is configured via a nested <Ssl> element.\u000a  *  The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.\u000aThis issue does not affect users of the HTTP appender, which uses a separate  verifyHostname https://logging.apache.org/log4j/2.x/manual/appenders/network.html#HttpAppender-attr-verifyHostName  attribute that was not subject to this bug and verifies host names by default.\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34477\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34477](https://avd.aquasec.com/nvd/cve-2026-34477)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1444",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.25.3.jar(1,0): CVE-2026-34477: : CVE-2026-34477: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34477**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34477](https://avd.aquasec.com/nvd/cve-2026-34477)|\u000a\u000aThe fix for  CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161  was incomplete: it addressed hostname verification only when enabled via the  log4j2.sslVerifyHostName https://logging.apache.org/log4j/2.x/manual/systemproperties.html#log4j2.sslVerifyHostName  system property, but not when configured through the  verifyHostName https://logging.apache.org/log4j/2.x/manual/appenders/network.html#SslConfiguration-attr-verifyHostName  attribute of the <Ssl> element.\u000a\u000aAlthough the verifyHostName configuration attribute was introduced in Log4j Core 2.12.0, it was silently ignored in all versions through 2.25.3, leaving TLS connections vulnerable to interception regardless of the configured value.\u000a\u000aA network-based attacker may be able to perform a man-in-the-middle attack when all of the following conditions are met:\u000a\u000a  *  An SMTP, Socket, or Syslog appender is in use.\u000a  *  TLS is configured via a nested <Ssl> element.\u000a  *  The attacker can present a certificate issued by a CA trusted by the appender's configured trust store, or by the default Java trust store if none is configured.\u000aThis issue does not affect users of the HTTP appender, which uses a separate  verifyHostname https://logging.apache.org/log4j/2.x/manual/appenders/network.html#HttpAppender-attr-verifyHostName  attribute that was not subject to this bug and verifies host names by default.\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34477\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34477](https://avd.aquasec.com/nvd/cve-2026-34477)",
      "type" : "CVE-2026-34477"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-core-2.25.3.jar",
      "fingerprint" : "FALLBACK-637f0a4f",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34478: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34478**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34478](https://avd.aquasec.com/nvd/cve-2026-34478)|\u000a\u000aApache Log4j Core's  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.\u000a\u000aTwo distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:\u000a\u000a  *  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.\u000a  *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.\u000a\u000a\u000aUsers of the SyslogAppender are not affected, as its configuration attributes were not modified.\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34478\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34478](https://avd.aquasec.com/nvd/cve-2026-34478)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1444",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.25.3.jar(1,0): CVE-2026-34478: : CVE-2026-34478: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34478**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34478](https://avd.aquasec.com/nvd/cve-2026-34478)|\u000a\u000aApache Log4j Core's  Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in versions 2.21.0 through 2.25.3, is vulnerable to log injection via CRLF sequences due to undocumented renames of security-relevant configuration attributes.\u000a\u000aTwo distinct issues affect users of stream-based syslog services who configure Rfc5424Layout directly:\u000a\u000a  *  The newLineEscape attribute was silently renamed, causing newline escaping to stop working for users of TCP framing (RFC 6587), exposing them to CRLF injection in log output.\u000a  *  The useTlsMessageFormat attribute was silently renamed, causing users of TLS framing (RFC 5425) to be silently downgraded to unframed TCP (RFC 6587), without newline escaping.\u000a\u000a\u000aUsers of the SyslogAppender are not affected, as its configuration attributes were not modified.\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34478\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34478](https://avd.aquasec.com/nvd/cve-2026-34478)",
      "type" : "CVE-2026-34478"
    },
    {
      "addedAt" : 0,
      "authorEmail" : "-",
      "authorName" : "-",
      "baseName" : "log4j-core-2.25.3.jar",
      "category" : "",
      "columnEnd" : 0,
      "columnStart" : 0,
      "commit" : "-",
      "description" : "",
      "fileName" : "/usr/local/tomcat/webapps/govwayAPIConfig.war/WEB-INF/lib/log4j-core-2.25.3.jar",
      "fingerprint" : "FALLBACK-6610c7f6",
      "lineEnd" : 1,
      "lineStart" : 1,
      "message" : "CVE-2026-34480: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core's  XmlLayout https://logging.apache.org/log4j/2.x/ma ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34480**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)|\u000a\u000aApache Log4j Core's  XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the  XML 1.0 specification https://www.w3.org/TR/xml/#charsets  producing invalid XML output whenever a log message or MDC value contains such characters.\u000a\u000aThe impact depends on the StAX implementation in use:\u000a\u000a  *  JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.\u000a  *  Alternative StAX implementations (e.g.,  Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34480\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)",
      "moduleName" : "",
      "origin" : "trivy",
      "originName" : "Trivy Security Scanner",
      "packageName" : "-",
      "reference" : "1444",
      "severity" : "NORMAL",
      "toString" : "log4j-core-2.25.3.jar(1,0): CVE-2026-34480: : CVE-2026-34480: LanguageSpecificPackageVulnerability\u000a\u000aApache Log4j Core's  XmlLayout https://logging.apache.org/log4j/2.x/ma ...\u000a\u000aFor additional help see: **Vulnerability CVE-2026-34480**\u000a| Severity | Package | Fixed Version | Link |\u000a| --- | --- | --- | --- |\u000a|MEDIUM|org.apache.logging.log4j:log4j-core|2.25.4|[CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)|\u000a\u000aApache Log4j Core's  XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the  XML 1.0 specification https://www.w3.org/TR/xml/#charsets  producing invalid XML output whenever a log message or MDC value contains such characters.\u000a\u000aThe impact depends on the StAX implementation in use:\u000a\u000a  *  JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.\u000a  *  Alternative StAX implementations (e.g.,  Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.\u000a\u000a\u000aUsers are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.\u000a\u000aPackage: org.apache.logging.log4j:log4j-core\u000aInstalled Version: 2.25.3\u000aVulnerability CVE-2026-34480\u000aSeverity: MEDIUM\u000aFixed Version: 2.25.4\u000aLink: [CVE-2026-34480](https://avd.aquasec.com/nvd/cve-2026-34480)",
      "type" : "CVE-2026-34480"
    }
  ],
  "size" : 3,
  "toString" : "3 warnings (normal: 3)"
}