Skip to content
Fencer Intel
critical —

GHSA-94g7-hpv8-h9qm json

Remote code injection in Log4j

published 4y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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](mailto:devinfo@splunk.com)

Patch / fix

  • maven com.splunk.logging:splunk-library-javalogging 1.6.2-0-0, 1.11.1

Is GHSA-94g7-hpv8-h9qm in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
maven com.splunk.logging:splunk-library-javalogging
>=1.7.0, <1.11.1
<1.6.2-0-0
1.11.1
1.6.2-0-0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.