E Business SuiteApplication · Oracle

CVE-2024-21269

HIGH · 8.1 CVSS v3.1 Published 2024-10-15
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 Incentive Compensation product of Oracle E-Business Suite (component: Compensation Plan). 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 Incentive Compensation. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Incentive Compensation accessible data as well as unauthorized access to critical data or complete access to all Oracle Incentive Compensation 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

HTTP-based vulnerability in Oracle Incentive Compensation's Compensation Plan component allows authenticated low-privilege attackers to create, delete, or modify critical data, as well as gain unauthorized access to sensitive data. The flaw is easily exploitable over the network with no user interaction required.

MitigationApply the relevant Oracle Critical Patch Update for this vulnerability. As an interim measure, restrict network access to the Oracle E-Business Suite interfaces and implement additional authentication controls, though Oracle patches are required for definitive remediation.

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
E Business SuiteApplication
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
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 installation
    Locate and confirm the Oracle EBS installation directory and verify the application server is running. Common paths include $ORACLE_HOME/apps or $EBS_HOME. Check for Oracle HTTP Server or Oracle Application Server processes.
    Affected if Oracle E Business Suite is installed and running
  2. Check EBS version number
    Query the Oracle EBS version using the command 'adident Header $EBS_HOME/apps/au/12.0.0/bin/xxxx' or check the README file in the installation directory. Alternatively, log into Oracle Applications Manager (OAM) and navigate to the version information page.
    Affected if Version is 12.2.3 through 12.2.13 inclusive
  3. Verify Incentive Compensation module is configured
    Check if the Oracle Incentive Compensation module is enabled in the EBS instance. This can be done by reviewing the installed modules in Oracle Applications Manager or checking the database for IC_X tables and IC_VIEWS schemas. Look for the presence of 'Compensation Plan' responsibility.
    Affected if Incentive Compensation with Compensation Plan component is installed and enabled
  4. Confirm HTTP accessibility of EBS interfaces
    Verify the Oracle EBS web interfaces (Oracle Application Framework/OAF pages) are network-accessible. Check the HTTP server configuration in httpd.conf or Oracle HTTP Server config. Test if the /OA_HTML/ directory is reachable over HTTP/HTTPS.
    Affected if EBS HTTP interfaces are exposed to the network (not restricted to localhost or VPN)
  5. Review user account privileges
    Examine existing EBS user accounts and their assigned responsibilities. Focus on identifying low-privilege users who have access to the Incentive Compensation module. Query the FND_USER table for user accounts and their associated responsibilities.
    Affected if Low-privilege user accounts exist with access to the Incentive Compensation module

The environment is affected if Oracle EBS version 12.2.3 through 12.2.13 is running with the Incentive Compensation Compensation Plan component enabled and accessible via HTTP, as the CVE allows authenticated low-privilege attackers to exploit the vulnerability over the 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 for this vulnerability. As an interim measure, restrict network access to the Oracle E-Business Suite interfaces and implement additional authentication controls, though Oracle patches are required for definitive remediation.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.13 (terminal release - apply quarterly security patches)

  1. 1. Navigate to My Oracle Support (support.oracle.com) and search for CVE-2024-21269 or the January 2025 Critical Patch Update (CPU).
  2. 2. Locate the specific patch for Oracle E-Business Suite 12.2.x addressing the Oracle Incentive Compensation component (Compensation Plan).
  3. 3. Download the applicable patch following Oracle's standard patch retrieval procedures.
  4. 4. Apply the patch following Oracle E-Business Suite standard patch application procedures, which typically involves: running ADPatch or OPatch as applicable, backing up the environment, and testing in a non-production environment first.
  5. 5. Verify the patch was applied successfully and test the Oracle Incentive Compensation functionality.
Caveat Standard patch application risks apply - test thoroughly in non-production first

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

Fix this in E Business Suite Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-21269 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