# CVE-2022-0070: Log4j hot patch package privilege escalation

> An incomplete fix in the Log4j hotpatch package allows attackers to escalate privileges by mimicking target process capabilities.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x6m6-c6mx-qvf8

## What is CVE-2022-0070?

CVE-2022-0070 is a high-severity vulnerability in Amazon Web Services log4j-cve-2021-44228-hotpatch, published on 19 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incomplete fix for CVE-2021-3100. The Apache Log4j hotpatch package starting with log4j-cve-2021-44228-hotpatch-1.1-16 will now explicitly mimic the Linux capabilities and cgroups of the target Java process that the hotpatch is applied to.

Weakness: CWE-269 (Improper Privilege Management), CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2022-0070?

It affects 1 product.


Products: Amazon Log4jhotpatch.

## How do I fix CVE-2022-0070?

No fix has been published for CVE-2022-0070 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0070 being exploited?

There is no known exploitation of CVE-2022-0070 in the wild and no public exploit code.

## Other vulnerabilities in Amazon Web Services log4j-cve-2021-44228-hotpatch

- [CVE-2021-3100](https://insights.sbomify.com/CVE-2021-3100/): Log4j hot patch package privilege escalation (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0070 and fix it if it is affected.

What it is: CVE-2022-0070 is a high-severity vulnerability in Amazon Web Services log4j-cve-2021-44228-hotpatch, published on 19 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0070 in the wild and no public exploit code.

Affected product: Amazon Web Services log4j-cve-2021-44228-hotpatch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0070/ (Markdown: https://insights.sbomify.com/CVE-2022-0070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0070
- OSV: https://osv.dev/vulnerability/CVE-2022-0070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0070/
Summaries are generated and may contain mistakes; the official description above is the record.