E Business SuiteApplication · Oracle

CVE-2024-21282

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

NVD · unedited

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

dbcve analysis · high confidence

Vulnerability in Oracle E-Business Suite Financials Common Components allows low-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to sensitive data. The attack requires no user interaction and exploits the application's handling of HTTP requests.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2024-21282 to Oracle E-Business Suite versions 12.2.3-12.2.13. Until patch is available, restrict network access to the EBS application to trusted IPs only.

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

Affected products & versions

NVD · CPE data

E Business SuiteApplication

Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown

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?

dbcve checks

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

Identify Oracle E-Business Suite installation

Check for Oracle E-Business Suite processes or look for the EBS web listener (Oracle HTTP Server) responding on standard ports (8000, 8001, 8080). Query the database for the version: SELECT release_name FROM apps.fnd_product_groups; or check the $APPL_TOP/../oa_html/US/<invalid focus> directory exists.

Affected if Oracle E-Business Suite is not installed or no EBS HTTP listener is running.
Determine the installed EBS version

Run SQL query: SELECT release_name FROM apps.fnd_product_groups; or check the Oracle Applications Manager (OAM) interface, or inspect the context file at $INST_TOP/appl/admin/<context_name>.xml for the variable s_weboam_core_version or similar.

Affected if The version is outside the range 12.2.3 through 12.2.13.
Verify version is within affected range

Compare the obtained version number to the affected range: >= 12.2.3 and <= 12.2.13. Any version within this inclusive range is potentially vulnerable.

Affected if Version falls between 12.2.3 and 12.2.13 inclusive.
Confirm Financials module is enabled

Check if the Oracle Financials module is licensed and enabled. Query: SELECT application_name, status FROM fnd_application_vl WHERE application_name LIKE '%Financial%'; or check via Oracle Applications Manager under License Manager.

Affected if Oracle Financials Common Components module is installed and enabled.
Assess network exposure

Review firewall rules, load balancer configurations, or network ACLs controlling access to the EBS HTTP ports (typically 8000, 8080, 443). Determine if the application is accessible from untrusted/network-facing interfaces.

Affected if The EBS HTTP interface is accessible from untrusted or external networks without IP restriction.

A user is affected if Oracle E-Business Suite version 12.2.3-12.2.13 is running with Financials enabled and the HTTP interface is accessible from untrusted networks.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.13

Interim mitigation

Apply Oracle Critical Patch Update (CPU) for CVE-2024-21282 to Oracle E-Business Suite versions 12.2.3-12.2.13. Until patch is available, restrict network access to the EBS application to trusted IPs only.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.13 is the latest 12.2.x release; consider upgrading to 12.2.14 or later if available (note: 12.2.14 may not exist yet - verify with Oracle)

Apply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite - check Oracle's Critical Patch Updates page for the quarterly release that addresses CVE-2024-21282
Apply Oracle E-Business Suite-specific patches from Oracle Support for this vulnerability - contact Oracle Support or search My Oracle Support for patch ID related to this CVE
After applying patches, verify the fix by reviewing Applied Patches in Oracle Applications Manager (OAM)
Ensure the Oracle Financials application is restarted if required by the patch instructions
Verify the fix does not break existing functionality by testing critical financial workflows

Caveat Contact Oracle Support before patching to confirm compatibility with customizations and integrated third-party applications; some patches may require downtime

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-21282 — 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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-21282?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 12.2.13 or later

Severity 8.1 High

Exploit likelihood EPSS, next 30 days 0.4%

Affects: E Business Suite

Remediation

A high-priority fix

Fix this in E Business Suite 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-21282 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References