E Business SuiteApplication · Oracle

CVE-2022-21587

CRITICAL · 9.8 CVSS v3.1 Published 2022-10-18

Fix available

A fix is available. Upgrade to after 12.2.11 or later.

See remediation →

100/100

Remediation priority · Urgent

In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Vulnerability in the Oracle Web Applications Desktop Integrator product of Oracle E-Business Suite (component: Upload). Supported versions that are affected are 12.2.3-12.2.11. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Web Applications Desktop Integrator. Successful attacks of this vulnerability can result in takeover of Oracle Web Applications Desktop Integrator. 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

A critical unauthenticated remote code execution vulnerability in the Upload component of Oracle Web Applications Desktop Integrator (E-Business Suite 12.2.3-12.2.11). Attackers can exploit this via HTTP requests without credentials, achieving complete system compromise (full confidentiality, integrity, and availability impact).

MitigationApply Oracle Critical Patch Update (CPU) for October 2022 or later that addresses CVE-2022-21587. If immediate patching is not possible, restrict network access to the Oracle EBS application tier via firewall or ACLs.

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

E Business SuiteApplication

Affected:>= 12.2.3, <= 12.2.11

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 E-Business Suite installation

Locate the Oracle E-Business Suite installation and determine the version by checking the APPL_TOP version file or using the Oracle AD Administration utility (adident Version $Header: adwctx.xml)

Affected if Oracle E-Business Suite is present and version falls within 12.2.3 to 12.2.11 inclusive
Confirm Web Applications Desktop Integrator component

Check if the Oracle Web Applications Desktop Integrator (WAD) module is installed by examining the Oracle Applications Manager (OAM) console or querying the FND_PRODUCT_INSTALLATIONS table

Affected if WAD component is installed and registered in the E-Business Suite environment
Verify upload functionality is accessible

Check if the /oa_servlets/ oracle.jsp.wwa.upload.controller.FileUploadController endpoint or similar WAD upload URLs are reachable via HTTP/HTTPS from the network

Affected if The upload servlet is exposed and accessible over the network without authentication
Review network accessibility

Examine network configuration to determine if the WAD upload endpoint is exposed externally or accessible from untrusted networks by reviewing web server configuration (Oracle HTTP Server or Oracle Web Listener) and firewall rules

Affected if The upload component is accessible from network segments that are not trusted or from the internet

A user is affected if Oracle E-Business Suite version 12.2.3 through 12.2.11 is installed with the Web Applications Desktop Integrator component enabled and its upload functionality is network-accessible.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.11

Vendor patch www.oracle.com →

Interim mitigation

Apply Oracle Critical Patch Update (CPU) for October 2022 or later that addresses CVE-2022-21587. If immediate patching is not possible, restrict network access to the Oracle EBS application tier via firewall or ACLs.

Recommended fix High confidence

Apply Oracle Critical Patch Update January 2022 (or later CPU) for E-Business Suite 12.2.3-12.2.11

Obtain the Oracle Critical Patch Update (CPU) for January 2022 or later from Oracle Support (.oracle.com)
Review the CPU patchea for Oracle E-Business Suite 12.2.3 through 12.2.11
Apply the security patch in a test environment first to validate compatibility
Schedule an appropriate maintenance window for production deployment
Apply the CPU patch to all affected E-Business Suite instances following Oracle's standard patch application procedures
Verify the patch was applied successfully and the vulnerability is remediated
As a temporary mitigation before patching, restrict network access to the Web Applications Desktop Integrator Upload component to trusted IPs only via web server or load balancer configuration

Caveat Patches may require downtime and should be tested in non-production first; some patches may require additional prerequisite patches

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

Fix this in E Business Suite Exploited in the wild — priority engagement

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-21587 — 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.comPatch / commit
packetstormsecurity.comProof of Concept
www.oracle.comPatchVendor Advisory
packetstormsecurity.comExploitThird Party AdvisoryVDB Entry
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-21587?

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 2023-02-23

A fix existsUpgrade to after 12.2.11 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 98.3%

Affects: E Business Suite

Remediation

Being exploited — close it fast

Fix this in E Business Suite 9 hrs · Moderate

Typical engagement from $1,600

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