[oagitm] A Vulnerability in Apache Log4j Could Allow for Arbitrary Code Execution - PATCH: NOW - TLP: WHITE

From: "MASSE THERESA" <dmarc-noreply@xxxxxxxxxxxxx> ("theresa.masse")
To: "oagitm@xxxxxxxxxxxxx" <oagitm@xxxxxxxxxxxxx>
Date: Mon, 13 Dec 2021 18:45:49 +0000

FYSA

SUBJECT:
A Vulnerability in Apache Log4j Could Allow for Arbitrary Code Execution

OVERVIEW:
A vulnerability has been discovered in Apache Log4j, a very ubiquitous logging
package for Java. Successful exploitation of this vulnerability could allow for
arbitrary code execution within the context of the systems and services that
use the Java logging library, including many services and applications written
in Java. Depending on the privileges associated with these systems and
services, an attacker could then install programs; view, change, or delete
data; or create new accounts with full user rights. If these systems and
services have been configured to have fewer user rights, exploitation of this
vulnerability could have less impact than if they were configured with
administrative rights.

THREAT INTELLIGENCE:
According to numerous open source reports, Log4j is used with Apache software
like Apache Struts, Solr, Druid, along with other technologies. Many websites
of manufacturers and providers have been found to be affected including Apple,
Twitter, Steam, Tesla and more. Threat actors will likely include payloads in
simple HTTP connections, either in a User-Agent header or trivial POST form
data. In addition, it has been reported that organizations are already seeing
signs of exploitation in the wild with further attempts on other websites
likely.

SYSTEMS AFFECTED:

  *   Apache Log4j between versions 2.0 and 2.14.1

RISK:
Government:

  *   Large and medium government entities: High
  *   Small government entities: High
Businesses:

  *   Large and medium business entities: High
  *   Small business entities: High
Home users: High

TECHNICAL SUMMARY:
A vulnerability has been discovered in Apache Log4j, a very ubiquitous logging
package for Java. This vulnerability resides in the JNDI lookup feature of the
log4j library. The JNDI lookup feature of log4j allows variables to be
retrieved via JNDI - Java Naming and Directory Interface. This is an API that
provides naming and directory functionality to Java applications. While there
are many possibilities, the log4j API supports LDAP and RMI (Remote Method
Invocation). An attacker who can control log messages or log message parameters
can execute arbitrary code loaded from LDAP servers when message lookup
substitution is enabled.

Successful exploitation of this vulnerability could allow for arbitrary code
execution within the context of the systems and services that use the Java
logging library, including many services and applications written in Java.
Depending on the privileges associated with these systems and services, an
attacker could then install programs; view, change, or delete data; or create
new accounts with full user rights. If these systems and services have been
configured to have fewer user rights, exploitation of this vulnerability could
have less impact than if they were configured with administrative rights.

RECOMMENDATIONS:
We recommend the following actions be taken:
·       Apply the latest patches (version 2.15.0) provided by Apache after
appropriate testing.
·       Run all systems and services as a non-privileged user (one without
administrative privileges) to diminish the effects of a successful attack.
·       Apply the Principle of Least Privilege to all systems and services.

December 13th – UPDATED RECOMMENDATIONS:

  *   Run the “Log4Shell” Vulnerability Tester provided by Huntress to test
whether your applications are vulnerable to CVE-2021-44228 (please see
references for the Huntress link).
  *   Check the GitHub repository listed in the reference section to see all
the Security Advisories & Bulletins related to CVE-2021-44228, which include
applications affected, version numbers, and the associated patches that should
be implemented if you have the affected version in your environment.

REFERENCES:

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228<https://urldefense.us/v3/__https:/cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT1ogp0jTY$>

SANS Technology Institute:
https://isc.sans.edu/diary/28120<https://urldefense.us/v3/__https:/isc.sans.edu/diary/28120__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT1owHdLOo$>

ZDNet:
https://www.zdnet.com/article/security-warning-new-zero-day-in-the-log4j-java-library-is-already-being-exploited/<https://urldefense.us/v3/__https:/www.zdnet.com/article/security-warning-new-zero-day-in-the-log4j-java-library-is-already-being-exploited/__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT14wkXyQ4$>

Ars Technica:
https://arstechnica.com/information-technology/2021/12/minecraft-and-other-apps-face-serious-threat-from-new-code-execution-bug/<https://urldefense.us/v3/__https:/arstechnica.com/information-technology/2021/12/minecraft-and-other-apps-face-serious-threat-from-new-code-execution-bug/__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT1SMxudoQ$>

December 13th – UPDATED REFERECENCES:

GitHub:
https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592<https://urldefense.us/v3/__https:/gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT1Khv2wdU$>

Huntress Log4Shell Tool:
https://log4shell.huntress.com/<https://urldefense.us/v3/__https:/log4shell.huntress.com/__;!!BClRuOV5cvtbuNI!R5XZNW2AbHkg9JiqdsaVOC59YISlU01O1H1tyemlTC_3kdLPuZyAglnKDBiJrVT1DXFcBAI$>

Theresa A. Masse
Cyber Security Advisor, Region 10 (Oregon)
Cybersecurity and Infrastructure Security Agency
Department of Homeland Security
Phone: (503) 930-5671
Email: theresa.masse@xxxxxxxxxxxx<mailto:theresa.masse@xxxxxxxxxxxx>

[cid:image007.png@01D7F00E.95D2D670]

[oagitm] A Vulnerability in Apache Log4j Could Allow for Arbitrary Code Execution - PATCH: NOW - TLP: WHITE

Other related posts: