# [HIGH] Find and fix the Log4Shell exploit fast with Snyk

**Source:** Snyk
**Published:** 2021-12-13
**Article:** https://snyk.io/blog/find-fix-log4shell-quickly-snyk/

## Threat Profile

Snyk Blog In this article
Written by Ariel Ornstein 
December 13, 2021
0 mins read Editor's note (28 Dec 2021 at 7:35 p.m. GMT): The Log4j team released a new security update that found 2.17.0 to be vulnerable to remote code execution, identified by CVE-2021-44832. We recommend upgrading to the latest version, which at this time is 2.17.1. Read more here .
Editor's note (18 Dec 2021 at 6:55 p.m. GMT): The Log4j situation is rapidly changing and we are updating our blogs as new information become…

## Indicators of Compromise (high-fidelity only)

- **CVE:** `CVE-2021-44832`
- **CVE:** `CVE-2021-44228`
- **CVE:** `CVE-2021-45046`
- **CVE:** `CVE-2021-45105`

## MITRE ATT&CK Techniques

- **T1190** — Exploit Public-Facing Application

## Kill chain phases observed

_(none detected from narrative keywords)_

## Recommended hunts

### IOC-driven hunts (use shared templates)

These are standard IOC-substitution hunts — the canonical SPL and KQL live once in [`_TEMPLATES.md`](../_TEMPLATES.md), so we don't repeat the same boilerplate on every CVE / hash / network-IOC briefing.

- **Asset exposure — vulnerability matches article CVE(s)** ([template](../_TEMPLATES.md#asset-exposure)) — phase: **recon**, confidence: **High**
  - CVE(s): `CVE-2021-44832`, `CVE-2021-44228`, `CVE-2021-45046`, `CVE-2021-45105`


## Why this matters

Severity classified as **HIGH** based on: CVE present, 1 use case(s) fired, 1 technique(s) inferred. Read the full article for actor attribution, tooling details, and any defanged IOCs in the body that aren't visible in the RSS summary.