dbcve.org
WorkflowApplication · Oracle

CVE-2024-21071

CRITICAL · 9.1 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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.

NVD · unedited
Vulnerability in the Oracle Workflow product of Oracle E-Business Suite (component: Admin Screens and Grants UI). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Workflow. While the vulnerability is in Oracle Workflow, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Workflow. CVSS 3.1 Base Score 9.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

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.

dbcve analysis · high confidence

Critical vulnerability in Oracle Workflow's Admin Screens and Grants UI component of Oracle E-Business Suite. Allows a high privileged attacker with network access via HTTP to completely take over Oracle Workflow, potentially impacting additional integrated products due to scope change.

MitigationApply the Oracle Critical Patch Update for CVE-2024-21071. Restrict network access to Oracle Workflow admin interfaces to high privileged users only.

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

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.

NVD · CPE data
WorkflowApplication
Affected:>= 12.2.3, <= 12.2.13

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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.

dbcve checks

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

  1. Identify Oracle E-Business Suite installation
    Check if Oracle E-Business Suite is installed in the environment by looking for Oracle application directories or checking the Oracle inventory
    Affected if E-Business Suite is present but version of Oracle Workflow cannot be determined
  2. Determine Oracle Workflow version
    Access Oracle Workflow Administrator responsibility and navigate to 'About This Page' or use the Oracle Workflow version query. Alternatively, check the WF_VERSION or WF_EVENT_PKG version from the database
    Affected if Installed version falls within range >= 12.2.3 and <= 12.2.13
  3. Verify Admin Screens component is accessible
    Check if the Oracle Workflow 'Admin Screens' or 'Grants UI' responsibility is assigned to any user in the system. Query FND_RESPONSIBILITY or FND_USER tables for Workflow Admin responsibilities
    Affected if Admin Screens or Grants UI component is enabled and accessible to any application user
  4. Assess network exposure of Workflow admin interfaces
    Review network configuration and access controls around the Oracle E-Business Suite web entry points, specifically the /OA_HTML/wf/ or /OA_HTML/plesk/wf/ admin directories. Check if these are accessible from untrusted networks
    Affected if Workflow admin interfaces are reachable from networks accessible to low-privilege or untrusted users

Environment is affected if Oracle Workflow version is 12.2.3 through 12.2.13 AND the Admin Screens/Grants UI component is enabled AND network access to the admin interface is possible for attackers.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply the Oracle Critical Patch Update for CVE-2024-21071. Restrict network access to Oracle Workflow admin interfaces to high privileged users only.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or latest 12.2.x release

  1. 1. Confirm current Oracle Workflow version by navigating to Oracle Application Manager > Oracle Workflow > Version
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Complete a full backup of the Oracle E-Business Suite database and application tier files
  4. 4. Apply the latest Oracle E-Business Suite 12.2.14 (or latest available) patch set update
  5. 5. Verify the upgrade completed successfully by checking the Oracle Workflow version again
  6. 6. Test critical Oracle Workflow administrative functions to confirm normal operation
Caveat Standard E-Business Suite upgrade considerations apply - review Oracle's upgrade documentation for customizations and integrations that may require testing or updates

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

Fix this in Workflow Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
38.0 hours of engineering $6,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21071 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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