E Business SuiteApplication · Oracle

CVE-2024-21278

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

An HTTP-based vulnerability in the Award Processes component of Oracle Contract Lifecycle Management for Public Sector allows low-privileged attackers to achieve unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to sensitive data. The CVSS vector indicates network exploitability with low attack complexity and no user interaction required, impacting both confidentiality and integrity at high levels.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21278 to the affected Oracle E-Business Suite deployment (versions 12.2.3-12.2.13), specifically targeting the Contract Lifecycle Management for Public Sector module.

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 version

Run the command 'select release_name from fnd_product_groups;' or check the $APPL_TOP/../oracle/apps/xx directory for version files, or access the Oracle Applications Manager (OAM) login page which displays the version

Affected if Version is >= 12.2.3 and <= 12.2.13
Confirm Contract Lifecycle Management for Public Sector module is installed

Query the database table 'FND_APPLICATION' for application name 'OKL' (Public Sector) or check the Oracle Applications Manager (OAM) > Applications > Modules Installed page for 'Contract Lifecycle Management for Public Sector'

Affected if The CLM PS module appears in the installed applications list
Verify Award Processes component is enabled

Check Oracle iSetup or functional setup manager for the 'Award Processes' module status under the CLM for Public Sector responsibility, or query 'FND_RESPONSIBILITY' for OKL responsibilities

Affected if Award Processes responsibility or feature is available to the user
Check HTTP access to CLM PS interfaces

Review the Oracle E-Business Suite listener configuration (_context.xml or httpd.conf) for URLs containing '/okl/' or '/oinc/' paths, and verify if the 'Award Processes' web entry points are accessible without authentication

Affected if HTTP endpoints for Award Processes are exposed and reachable over network

The environment is affected if Oracle E-Business Suite version is between 12.2.3 and 12.2.13 AND the Contract Lifecycle Management for Public Sector module with Award Processes component is installed and accessible.

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 the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21278 to the affected Oracle E-Business Suite deployment (versions 12.2.3-12.2.13), specifically targeting the Contract Lifecycle Management for Public Sector module.

Recommended fix Moderate confidence

Apply the relevant Oracle Critical Patch Update (CPU) that contains the fix for CVE-2024-21278; Oracle EBS 12.2.13 is the upper bound of the affected range - subsequent quarterly CPUs contain the fix

Navigate to Oracle Support and search for CVE-2024-21278 or the related Oracle Critical Patch Update (CPU) that addresses this vulnerability
Identify the specific Oracle E-Business Suite patch number for this CVE in the CPU advisory
Apply the appropriate Oracle EBS patch following Oracle's standard patch application procedures
Verify the patch was applied successfully by checking the Oracle applications version and testing the Award Processes component
Ensure the Oracle E-Business Suite system is backed up before applying any patches

Caveat Oracle EBS patches may require downtime and thorough testing in a non-production environment before production deployment; review all associated patch prerequisites and conflicts

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
Testing20.0 h
Review / QA8.0 h

46.0 hours of engineering $7,800

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-21278 — 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-21278 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-21278?

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 46 hrs · Moderate

Typical engagement from $7,800

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-21278 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