Application Development FrameworkApplication · Oracle

CVE-2022-21445

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-19

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

In the wild High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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).

Technical summary

dbcve analysis · high confidence

Critical unauthenticated remote code execution vulnerability in Oracle ADF Faces component of Oracle Fusion Middleware versions 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable via HTTP, allowing complete takeover of the Oracle Application Development Framework.

MitigationApply Oracle Fusion Middleware patches for CVE-2022-21445 as referenced in Fusion Middleware Patch Advisor. If immediate patching is not possible, restrict network access to ADF endpoints and implement web application firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Application Development FrameworkApplication

Affected:= 12.2.1.3.0= 12.2.1.4.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle Fusion Middleware version

Locate the Oracle Fusion Middleware installation directory and check the inventory.xml file (typically in $ORACLE_HOME/inventory/ContentsXML) or check the About Oracle Fusion Middleware page in WebLogic Administration Console

Affected if The installed version is exactly 12.2.1.3.0 or 12.2.1.4.0
Confirm ADF Faces component is present

Check if the application deployment includes ADF Faces libraries. In WebLogic Administration Console, navigate to Deployments and look for applications using 'adf-faces' or 'Oracle ADF Faces' component

Affected if ADF Faces is deployed and enabled in the application
Verify HTTP endpoint exposure

Inspect the web application's web.xml descriptor (found in the WAR deployment under WEB-INF/web.xml) and check for FacesServlet mappings that expose ADF Faces endpoints over HTTP

Affected if The FacesServlet is mapped and accessible via HTTP (typically at /faces/* or *.jspx paths)
Check network accessibility of ADF endpoints

Review the WebLogic network configuration to determine if ADF-facing HTTP ports are accessible from untrusted networks. Check the ListenAddress and ListenPort settings in the server configuration

Affected if ADF HTTP endpoints are reachable from external or untrusted networks without network segmentation

You are affected if Oracle Fusion Middleware version is exactly 12.2.1.3.0 or 12.2.1.4.0 AND ADF Faces is exposed via accessible HTTP endpoints.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Fusion Middleware patches for CVE-2022-21445 as referenced in Fusion Middleware Patch Advisor. If immediate patching is not possible, restrict network access to ADF endpoints and implement web application firewall rules.

Recommended fix High confidence

Oracle Fusion Middleware 12.2.1.5.0 or later (if available) or apply Oracle CPU patches to existing 12.2.1.3.0/12.2.1.4.0 installations

1. Identify the exact Oracle CPUs (Critical Patch Updates) or patches applicable to your Oracle Fusion Middleware installation from Oracle Support.
2. Subscribe to Oracle Critical Patch Updates to receive security patches (Oracle releases these quarterly).
3. Apply the April 2022 Critical Patch Update (CPU) which addresses CVE-2022-21445, or apply the specific patch for this vulnerability if released as an out-of-band patch.
4. For Oracle ADF downloaded via JDeveloper, ensure both the JDeveloper IDE and the ADF runtime libraries on all application servers are patched.
5. After applying the patch, restart all affected Oracle WebLogic Server instances and ADF applications.
6. Verify the patch was applied correctly by checking the Oracle OPatch utility output and testing the ADF applications.

Caveat Oracle CPU patches typically include regression fixes and are safe to apply; verify application functionality after patching

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Application Development Framework Exploited in the wild — priority engagement

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA6.0 h

42.0 hours of engineering $7,360

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-21445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21445 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-21445?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2024-10-09

A fix existsA vendor remedy is published

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 62.5%

Affects: Application Development Framework

Remediation

Being exploited — close it fast

Fix this in Application Development Framework 42 hrs · Moderate

Typical engagement from $7,360

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References