dbcve.org
PurchasingApplication · Oracle

CVE-2024-21132

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Purchasing product of Oracle E-Business Suite (component: Approvals). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Purchasing. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Purchasing, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Purchasing accessible data as well as unauthorized read access to a subset of Oracle Purchasing accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 access control vulnerability in Oracle E-Business Suite Purchasing's Approvals component. A low-privileged attacker with network access can exploit this flaw to gain unauthorized read and write access to a subset of Oracle Purchasing data. The attack requires human interaction and can impact additional products due to scope change (CVSS scope changed).

MitigationApply the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses CVE-2024-21132. Since no workarounds are mentioned, patching is the primary remediation path.

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
PurchasingApplication
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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Confirm Oracle E-Business Suite is installed
    Identify whether Oracle E-Business Suite is deployed in your environment by checking for Oracle Application Server or Oracle E-Business Suite processes and installations
    Affected if Oracle E-Business Suite is not present, the vulnerability does not apply
  2. Check Oracle Purchasing module version
    Use Oracle's version checking utilities or query the Oracle Purchasing version from the application. The affected range is >= 12.2.3 and <= 12.2.13
    Affected if The installed Oracle Purchasing version falls within 12.2.3 through 12.2.13 inclusive
  3. Verify Approvals component is enabled
    Check if the Oracle Purchasing Approvals component is configured and active in your E-Business Suite instance
    Affected if The Approvals component is not in use, the specific attack surface may be reduced
  4. Assess network accessibility
    Determine if the Oracle E-Business Suite web interfaces are exposed to the network, as the vulnerability requires network access for exploitation
    Affected if The application is only accessible from completely isolated local networks without external access, the attack vector may be limited

You are affected if Oracle E-Business Suite with Oracle Purchasing version 12.2.3 through 12.2.13 is running with the Approvals component enabled and accessible over a 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 relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses CVE-2024-21132. Since no workarounds are mentioned, patching is the primary remediation path.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later (which includes the fix for CVE-2024-21132)

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21132. For Oracle E-Business Suite 12.2.x, this is typically included in the April 2024 CPU or later.
  2. Navigate to Oracle Support and download the appropriate patch for your specific Oracle E-Business Suite 12.2.x version (12.2.3 through 12.2.13).
  3. Review Oracle Support Document 248417.1 (Oracle E-Business Suite Patch Application Guide) for proper patching procedures.
  4. Before applying the patch, perform a full backup of the Oracle E-Business Suite environment including the database, Oracle Application tier, and Oracle WebLogic tier.
  5. Stop all Oracle E-Business Suite services using the adapcctl.sh and adcmctl.sh scripts.
  6. Apply the patch using ADPatch (adpatch) following Oracle's standard patching methodology.
  7. After patching, verify the patch was applied successfully using the adph show=applied command.
  8. Restart all Oracle E-Business Suite services.
Caveat Standard Oracle E-Business Suite patching risks apply - test thoroughly in a non-production environment before applying to production; some customizations may require revalidation after patch application

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

Fix this in Purchasing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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