GHSA-94g7-hpv8-h9qm
Remote code injection in Log4j
Blast Radius
com.splunk.logging:splunk-library-javalogging☕com.splunk.logging:splunk-library-javaloggingReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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 [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.splunk.logging:splunk-library-javalogging | ≥ 1.7.0&&< 1.11.1 | 1.11.1 |
| ☕Maven | com.splunk.logging:splunk-library-javalogging | all versions | 1.6.2-0-0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.splunk.logging:splunk-library-javalogging. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.splunk.logging:splunk-library-javalogging to 1.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-94g7-hpv8-h9qm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-94g7-hpv8-h9qm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-94g7-hpv8-h9qm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-94g7-hpv8-h9qm in your dependencies?
O3 detects GHSA-94g7-hpv8-h9qm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.