dbcve.org
E Business SuiteApplication · Oracle

CVE-2024-21279

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 Sourcing product of Oracle E-Business Suite (component: Auctions). 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 Sourcing. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Sourcing accessible data as well as unauthorized access to critical data or complete access to all Oracle Sourcing 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

Oracle Sourcing Auctions component in E-Business Suite versions 12.2.3-12.2.13 contains an HTTP-based vulnerability exploitable by low-privileged attackers, allowing unauthorized creation, deletion, or modification of critical data as well as unauthorized access to sensitive information.

MitigationApply Oracle Critical Patch Update (CPU) or specific patch for CVE-2024-21279; restrict network access to Oracle Sourcing HTTP endpoints and implement WAF rules as compensating controls until patch is applied.

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 the Oracle E-Business Suite installation directory or check for Oracle application processes running on the system
    Affected if Oracle E-Business Suite is installed and running
  2. Determine the E-Business Suite version
    Use Oracle administrative commands or check version files in the installation directory to obtain the exact version number
    Affected if Version falls within 12.2.3 to 12.2.13 inclusive
  3. Verify Oracle Sourcing component is enabled
    Check the Oracle Sourcing Auctions module configuration through Oracle Applications Manager or by querying the module status in the EBS database
    Affected if Oracle Sourcing Auctions component is enabled and accessible
  4. Check for HTTP endpoint exposure
    Inspect the Oracle HTTP server configuration or web listener settings to determine if the Sourcing module is exposed via HTTP
    Affected if HTTP-based access to Oracle Sourcing is enabled and externally accessible
  5. Review access controls on Sourcing module
    Examine the permission configuration for the Oracle Sourcing Auctions component to determine if low-privileged users can access sensitive functions
    Affected if Low-privileged or unauthenticated HTTP access to Sourcing functions is permitted

A user is affected if Oracle E-Business Suite version 12.2.3-12.2.13 is installed with the Oracle Sourcing Auctions component enabled and accessible via HTTP.

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 Oracle Critical Patch Update (CPU) or specific patch for CVE-2024-21279; restrict network access to Oracle Sourcing HTTP endpoints and implement WAF rules as compensating controls until patch is applied.

Recommended fix High confidence

Apply Oracle CPU October 2024 patch for Oracle E-Business Suite 12.2.x

  1. 1. Review Oracle Critical Patch Update (CPU) October 2024 for CVE-2024-21279
  2. 2. Download the applicable Oracle E-Business Suite patch from My Oracle Support (MOS)
  3. 3. Apply the patch in a non-production environment first to verify compatibility
  4. 4. Test critical Oracle Sourcing workflows (auctions, sourcing events) after patch application
  5. 5. Apply the patch to production during a scheduled maintenance window
  6. 6. Verify the patch was applied successfully by checking the AD applied patches table
  7. 7. Confirm Oracle Sourcing functionality works correctly post-patch
Caveat Patch may require downtime during maintenance window; test thoroughly in non-prod first

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

Fix this in E Business Suite 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-21279 — 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-21279 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