# CVE-2022-21445: Oracle ADF Faces Deserialization of Untrusted Data

> Unauthenticated attackers can achieve full system takeover via deserialization flaws in Oracle ADF Faces, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Sep 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-7f3x-fvqf-q6q5

## What is CVE-2022-21445?

CVE-2022-21445 is a critical unsafe deserialization vulnerability in Oracle Corporation Application Development Framework (ADF), published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Application Development Framework (ADF) product of Oracle Fusion Middleware (component: ADF Faces).  Supported versions that are affected are 12.2.1.3.0 and  12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Application Development Framework (ADF).  Successful attacks of this vulnerability can result in takeover of Oracle Application Development Framework (ADF). Note: Oracle Application Development Framework (ADF) is downloaded via Oracle JDeveloper Product. Please refer to Fusion Middleware Patch Advisor for more details. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Oracle Application Development Framework.

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

No fix has been published for CVE-2022-21445 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Oct 2024.

## Is CVE-2022-21445 being exploited?

Yes. Attackers have exploited CVE-2022-21445 in the wild since at least 18 Sep 2024.

Public exploit code:

- https://github.com/hienkiet/CVE-2022-21445-for-12.2.1.3.0-Weblogic (github_poc): https://github.com/hienkiet/CVE-2022-21445-for-12.2.1.3.0-Weblogic
- Exploit for CVE-2022-21445 of Oracle Weblogic 12.2.1.X (github_poc): https://github.com/NeCr00/CVE-2022-21445

## Other vulnerabilities in Oracle Corporation Application Development Framework (ADF)

- [CVE-2026-35243](https://insights.sbomify.com/CVE-2026-35243/): Privilege escalation in Oracle Application Development Framework (ADF) (high 7.8)
- [CVE-2026-46769](https://insights.sbomify.com/CVE-2026-46769/): Auth bypass in Oracle Application Development Framework (ADF) (high 7.2)
- [CVE-2026-46770](https://insights.sbomify.com/CVE-2026-46770/): Missing authorization in Oracle Application Development Framework (ADF) (medium 6.1)
- [CVE-2026-46772](https://insights.sbomify.com/CVE-2026-46772/): Missing authorization in Oracle Application Development Framework (ADF) (medium 4.7)
- [CVE-2026-46771](https://insights.sbomify.com/CVE-2026-46771/): Missing authorization in Oracle Application Development Framework (ADF) (medium 4.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21445 is a critical unsafe deserialization vulnerability in Oracle Corporation Application Development Framework (ADF), published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-21445 in the wild since at least 18 Sep 2024.

Affected product: Oracle Corporation Application Development Framework (ADF). 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-21445/ (Markdown: https://insights.sbomify.com/CVE-2022-21445/index.md)
```

## Sources

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

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