cchesser/nr-find-log4j

Per CVE-2021-44228 and CVE-2021-45046, Apache log4j2 versions < 2.16.0 (except 2.12.2) are vulnerable to remote code execution and potential data exfiltration.

This script will scan your New Relic account(s) for java services that report usage of log4j-core, and generate a manifest containing each suspect service with the version of log4j-core reported by New Relic APM.

Note that this script may generate false positives and false negatives. It is intended to assist your own investigation of potentially vulnerable systems, and does not provide any strong guarantees or proof of non-vulnerability.

Usage

node nr-find-log4j.js

Requirements:

Node.js (tested on versions 12 and 14)
A New Relic User API Key

To get your New Relic API key, visit the New Relic API Key management page and either copy an existing USER key (use the 'Copy key' action in the '...' menu) or create a new key with the Create a key button.

Note: Even though user API keys are associated with an account, this script will be able to scan any account your user is authorized to access. You should not need to create an API key per account.

Executing this script will take some time if you have many java services.

Command-line options:

--csv           output findings in CSV format (default)
--json          output findings in JSON format
--all-services  include services that do NOT report presence of log4j-core

Output

The output includes all Java services found to contain log4j-core, the vulnerable library.

Our suggested analysis is:

Check the version of log4j-core. Versions 2.0 through < 2.16.0 (except 2.12.2) are known vulnerable.
Verify you have upgraded the New Relic agentVersion to a known-safe Java agent release.
Compare examinedInstances count on each service to the upgraded and mitigated instance counts to assess how many instances may still be vulnerable:
1. upgradedInstances indicates how many running instances have log4j-core ≥ 2.16 or 2.12.2. If all instances are "upgraded" then we did not detect a vulnerable version of the library.
2. mitigatedInstances indicates how many running instances have the -Dlog4j2.formatMsgNoLookups=true jvm argument applied.
Use the nrUrl link to directly examine the service's runtime environment as reported by the Java agent

The CSV and JSON files contain these fields:

accountId New Relic account id containing the service
applicationId New Relic application id of the service
name Display name of the service as seen in New Relic
examinedInstances Number of runtime instances of the service that were examined
upgradedInstances Number of examined instances that report using Log4j version 2.12.2 or 2.16+
mitigatedInstances Number of examined instances that report using the -Dlog4j2.formatMsgNoLookups=true JVM argument mitigation
agentVersion New Relic agent version detected in the service
log4jJar Name of the log4j-core jar file detected in the service
log4jJarVersion Version string of the log4j-core library detected in the service
log4jJarSha1 SHA1 hash of the log4j-core jar file
log4jJarSha512 SHA512 hash of the log4j-core jar file
nrUrl Link to the New Relic UI to examine the service's environment data

Auditing New Relic Java agent usage

Per Security Bulletin NR21-03, New Relic Java agent versions 7.4.1 and 6.5.1 contain updated Log4j2 libraries. To find out what version of the New Relic Java APM agent your services are running, use NRDB's ApplicationAgentContext events.

log into https://one.newrelic.com
click "Query your data" then select the "Query builder" tab
run this NRQL query against each of your accounts:

SELECT latest(agent.version) FROM ApplicationAgentContext 
WHERE agent.language = 'java' and agent.version not in ('7.4.1', '6.5.1') 
SINCE 1 week ago facet entity.guid, appName limit max

Support

New Relic has open-sourced this project. This project is provided AS-IS WITHOUT WARRANTY OR DEDICATED SUPPORT. Issues and contributions should be reported to the project here on GitHub.

We encourage you to bring your experiences and questions to the Explorers Hub where our community members collaborate on solutions and new ideas.

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

License

nr-find-log4j is licensed under the Apache 2.0 License.

Disclaimer

This tool is provided by New Relic AS IS, without warranty of any kind. New Relic does not guarantee that the tool will: not cause any disruption to services or systems; provide results that are complete or 100% accurate; correct or cure any detected vulnerability; or provide specific remediation advice.

cchesser / nr-find-log4j