Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Tenable 博客

订阅

Hot Patches for Log4Shell Introduced Multiple Vulnerabilities in Amazon Web Services

Hot Patches for Log4Shell Introduced Multiple Vulnerabilities in Amazon Web Services

Amazon Web Services has addressed vulnerabilities introduced by the hot patches released in response to the Log4Shell vulnerability in December.

背景

On April 19, researchers with Palo Alto’s Unit 42 disclosed four vulnerabilities introduced by the hot patches for Amazon Web Services (AWS) in response to CVE-2021-44228, also known as Log4Shell. While there are four CVEs, CVE-2022-0070 and CVE-2022-0071 were assigned to address incomplete patches for CVE-2021-3100 and CVE-2021-3101 respectively, which were initially disclosed in December 2021.

CVE 说明 CVSSv3
CVE-2021-3100 Apache Log4j Hot Patch Service Execution with Unnecessary Privileges Vulnerability 8.8
CVE-2021-3101 Hotdog Hot Patch Solution Execution with Unnecessary Privileges Vulnerability 8.8
CVE-2022-0070 Apache Log4j Hotpatch Service Execution with Unnecessary Privileges Vulnerability 8.8
CVE-2022-0071 Hotdog Hot Patch Solution Execution with Unnecessary Privileges Vulnerability (Incomplete Fix) 8.8

分析

On December 12, in response to the Log4Shell vulnerability, AWS released open source hot patches — short term solutions to be implemented at scale until a more robust fixed version can be deployed — for several environments. These hot patches detect vulnerable Java applications and patch them “on the fly.”

According to the researchers at Unit 42, the hot patch solutions developed to address Log4Shell for standalone servers, Kubernetes clusters, Elastic Container Service (ECS) clusters and Fargate contained “severe security issues.” These hot patches, though from AWS, can be applied to other cloud and on-prem environments.

These issues can be exploited by “every container in [the hot patched] environment” to achieve container escape and host takeover. The vulnerabilities also allow unprivileged processes to escalate privileges and gain code execution with root privileges. The vulnerabilities are not configuration-dependent, they can be exploited in most AWS environments.

解决方案

The following is a summary of the solutions for the hot patches:

解决方案 Fixed Version 发布
Amazon Linux (AMI) 1.1-16 log4j-cve-2021-44228-hotpatch
Kubernetes 1.1-16 kubernetes-log4j-cve-2021-44228-node-agent Daemonset
Bottlerocket 1.02 hotdog-v1.0.2

识别受影响的系统

A list of Tenable plugins to identify these vulnerabilities can be found here.

Tenable.cs users can detect vulnerable Kubernetes deployments via the kubernetes-log4j-cve-2021-44228-node-agent hot patch daemonset using open policy agent rego. The rego checks the image version, if it is "v0.0.12-debian" then it finds the corresponding configmap to check the actual package version that the daemonset job will install in the cluster. If Tenable.cs does not detect the fixed version (1.1-16), the product will display an alert.

获取更多信息

加入 Tenable Community 中的 Tenable 安全响应团队

了解有关 Tenable 这款首创 Cyber Exposure 平台的更多信息,全面管理现代攻击面。

获取 30 天免费试用 Tenable.io 漏洞管理平台的机会。

相关文章

您可加以利用的网络安全新闻

输入您的电子邮件,绝不要错过 Tenable 专家的及时提醒和安全指导。