# CVE-2022-23307: A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution.

> A deserialization flaw in the Chainsaw component of Log4j 1 allows attackers to execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jan 2022
- **Updated:** 27 May 2026
- **Also known as:** CLEANSTART-2026-QY70985, DEBIAN-CVE-2022-23307, GHSA-f7vh-qwp3-x37m, MINI-ggh8-rwx4-vgh6, MINI-m56g-rxvp-gr3v, ROOT-APP-MAVEN-CVE-2022-23307, UBUNTU-CVE-2022-23307

## What is CVE-2022-23307?

CVE-2022-23307 is a high-severity unsafe deserialization vulnerability in Oracle Business Intelligence, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

4 open source packages ship an affected version, including log4j:log4j and org.zenframework.z8.dependencies.commons:log4j-1.2.17. It affects 26 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `log4j:log4j` | Maven | All versions to 1.2.17 | None |
| `log4j:log4j` | Maven | All versions to 1.2.17 | None |
| `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions to 2.0 | None |
| `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions to 2.0 | None |

Products: Apache Chainsaw, Apache Log4j, Oracle Advanced Supply Chain Planning, Oracle Business Intelligence, Oracle Business Process Management Suite, Oracle Communications Eagle Ftp Table Base Retrieval, Oracle Communications Instant Messaging Server, Oracle Communications Messaging Server, Oracle Communications Network Integrity, Oracle Communications Offline Mediation Controller, Oracle Communications Unified Inventory Management, Oracle E-Business Suite Cloud Manager and Cloud Backup Module, Oracle Enterprise Manager Base Platform, Oracle Financial Services Revenue Management and Billing Analytics, Oracle Healthcare Foundation, Oracle Hyperion Data Relationship Management, Oracle Hyperion Infrastructure Technology, Oracle Identity Management Suite, Oracle Identity Manager Connector, Oracle Jdeveloper and 6 more.

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

Product is end of life, replace it.

## Is CVE-2022-23307 being exploited?

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

## Other vulnerabilities in Oracle Business Intelligence

- [CVE-2020-9493](https://insights.sbomify.com/CVE-2020-9493/): Java deserialization in Chainsaw (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23307 is a high-severity unsafe deserialization vulnerability in Oracle Business Intelligence, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23307 in the wild and no public exploit code.

Affected packages and fixed versions:
- log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed
- log4j:log4j (Maven): affected all versions up to 1.2.17; no fix listed
- org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed
- org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions up to 2.0; no fix listed

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-23307/ (Markdown: https://insights.sbomify.com/CVE-2022-23307/index.md)
```

## Sources

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

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