Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

com.splunk.logging:splunk-library-javalogging

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedMavenPublished

    Remote code injection in Log4j

    GHSA-94g7-hpv8-h9qm

    Affected
    • Maven com.splunk.logging:splunk-library-javalogging >= 1.7.0, < 1.11.1; < 1.6.2-0-0
    Fixed in
    1.11.11.6.2-0-0· Vendor fix available
    Issue
    Impact Logging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input. More Details: https://github.com/advisories/GHSA-jfh8-c2jp-5v3q Patches Version 1.11.1 of the Splunk Logging for Java library. There is also a backport to version 1.6.2 released as a patch: 1.6.2-0-0. Workarounds If upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components. References https://github.com/advisories/GHSA-jfh8-c2jp-5v3q For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/splunk/splunk-library-javalogging/issues Email us at devinfo@splunk.com

    Recommended action: Upgrade to 1.11.1 or 1.6.2-0-0 (pre-release) by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →