GHSA-94g7-hpv8-h9qm
Remote code injection in Log4j
GHSA-94g7-hpv8-h9qm is a vulnerability with no CVSS score yet in com.splunk.logging:splunk-library-javalogging, published December 14, 2021. No source lists public exploit code. Fixed in com.splunk.logging:splunk-library-javalogging 1.11.1.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
1.11.1com.splunk.logging:splunk-library-javalogging +1 more
Description
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
Affected packages
| Package | Affected | Fixed |
|---|---|---|
com.splunk.logging:splunk-library-javaloggingMaven | 1.7.0 up to 1.11.1 | 1.11.1 |
com.splunk.logging:splunk-library-javaloggingMaven | before 1.6.2-0-0 | 1.6.2-0-0 |
What each source reports
GitHub AdvisoriesNo score
Remote code injection in Log4j
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
- Record
GHSA-94g7-hpv8-h9qm- Updated
- 2026-11-02
OSVNo score
Remote code injection in Log4j
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
- Record
GHSA-94g7-hpv8-h9qm- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.