dbcve.org
Process Manufacturing FinancialsApplication · Oracle

CVE-2024-21152

HIGH · 8.1 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
87/100
Remediation priority · High
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 Process Manufacturing Financials product of Oracle E-Business Suite (component: Allocation Rules). Supported versions that are affected are 12.2.12-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Process Manufacturing Financials. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Process Manufacturing Financials accessible data as well as unauthorized access to critical data or complete access to all Oracle Process Manufacturing Financials accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

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

This is an authenticated vulnerability in Oracle Process Manufacturing Financials (E-Business Suite 12.2.12-12.2.13) affecting the Allocation Rules component. A low-privileged attacker with network access via HTTP can exploit this to achieve unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to sensitive or all accessible data. The CVSS 3.1 score of 8.1 reflects high confidentiality and integrity impacts with no availability impact.

MitigationApply the Oracle Critical Patch Update (CPU) or specific patch for CVE-2024-21152 to Oracle E-Business Suite 12.2.12-12.2.13. Verify that allocation rules functionality operates correctly after patching.

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
Process Manufacturing FinancialsApplication
Affected:>= 12.2.12, <= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 version
    Query the Oracle database or check the EBS admin console for the current version number. In Oracle EBS, you can typically run 'select release_name from apps.fnd_product_groups;' or check the About Oracle E-Business Suite page from the homepage.
    Affected if The installed version is 12.2.12 or 12.2.13, or falls within the range 12.2.12 through 12.2.13 inclusive.
  2. Confirm Allocation Rules component is present
    Navigate to the Oracle Process Manufacturing Financials module and verify the Allocation Rules sub-component is installed. Check the Oracle Applications Manager (OAM) or the functional responsibility setup for access to 'Allocation Rules' under the Manufacturing submenu.
    Affected if The Allocation Rules component is installed and visible in the Oracle Process Manufacturing Financials menu structure.
  3. Verify web interface accessibility
    Confirm the Oracle E-Business Suite HTML interface is accessible over HTTP/HTTPS. Test connectivity to the EBS login page URL (typically /OA_HTML/AppsLogin) from the network.
    Affected if The EBS web interface is reachable via HTTP, allowing network-based access to the application.
  4. Check Allocation Rules responsibility assignment
    Review the responsibility definitions in the Oracle EBS Security console (FND_RESPONSIBILITIES) to see if users can access the Allocation Rules function. Look for responsibilities granting access to 'Allocation Rules' or 'Process Manufacturing Financials' functions.
    Affected if Low-privileged users are assigned a responsibility that includes access to the Allocation Rules function.

You are affected if your Oracle E-Business Suite version is 12.2.12 or 12.2.13, the Allocation Rules component is present, and it is accessible via HTTP to authenticated users on your network.

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 (CPU) or specific patch for CVE-2024-21152 to Oracle E-Business Suite 12.2.12-12.2.13. Verify that allocation rules functionality operates correctly after patching.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 (latest 12.2.x release)

  1. 1. Review Oracle E-Business Suite 12.2.x supported upgrade paths in Oracle's official documentation
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Perform a complete backup of the Oracle E-Business Suite database, application tier, and configuration files
  4. 4. Test the upgrade in a non-production environment first to validate compatibility
  5. 5. Apply the latest Oracle E-Business Suite 12.2.14 (or latest 12.2.x) application tier patch
  6. 6. Run the Oracleadop (Online Patching) utility to apply the upgrade: adop phase=prepare, adop phase=apply, adop phase=finalize
  7. 7. Verify the Allocation Rules component functions correctly post-upgrade
  8. 8. Validate that the security fix for CVE-2024-21152 is applied by checking Oracle's patch inventory
Caveat Standard Oracle E-Business Suite upgrade risks apply - review Oracle's 12.2.14 release notes for any functional changes to Allocation Rules or related modules before upgrading

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

Fix this in Process Manufacturing Financials Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA4.0 h
25.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21152 — 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-21152 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