dbcve.org
Applications FrameworkApplication · Oracle

CVE-2024-21080

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Applications Framework product of Oracle E-Business Suite (component: REST Services). Supported versions that are affected are 12.2.9-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Applications Framework accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 authentication/authorization vulnerability in Oracle Applications Framework's REST Services component. Low-privileged users with network access via HTTP can exploit this to gain unauthorized access to critical data or complete access to all accessible data. The CVSS vector indicates no integrity or availability impact, suggesting the vulnerability allows horizontal or vertical privilege escalation in REST API endpoints.

MitigationApply Oracle's security patch for this vulnerability to all affected Oracle E-Business Suite instances (versions 12.2.9-12.2.13). Review REST service access controls and audit existing user permissions as a supplementary hardening measure.

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
Applications FrameworkApplication
Affected:>= 12.2.9, <= 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Applications Framework installation
    Locate the Oracle E-Business Suite installation and confirm the Oracle Applications Framework (OAF) component is present. Check for OAF-related directories or Oracle E-Business Suite version banners in the application.
    Affected if The system is running Oracle E-Business Suite with Oracle Applications Framework component installed.
  2. Check Oracle Applications Framework version
    Query the Oracle database or check the appltop directory for the OAF version. Use SQL query like 'SELECT patch_level FROM fnd_product_installations WHERE patch_level LIKE "%OAF%"' or check the OA_JAR/version.txt file in the appltop directory.
    Affected if The installed version is between 12.2.9 and 12.2.13 inclusive.
  3. Verify REST Services component is enabled
    Check the Oracle E-Business Suite REST Services configuration. Look for ICX/ICXPLUS/portal synonyms and REST service definitions in the database. Query the Oracle Application Framework REST service endpoints or check the active REST service registrations.
    Affected if REST Services (ICX) endpoints are configured and accessible via HTTP.
  4. Inspect REST service access control configuration
    Review the Oracle Application Framework REST Services access control lists (ACLs) and function security definitions. Check the ICX: Allow Anonymous Access profile option and REST service permission settings in the Oracle E-Business Suite.
    Affected if Low-privileged users have network access to REST API endpoints without proper authorization enforcement.

A system is affected if it runs Oracle Applications Framework version 12.2.9 through 12.2.13 with REST Services enabled and accessible to low-privileged network users.

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's security patch for this vulnerability to all affected Oracle E-Business Suite instances (versions 12.2.9-12.2.13). Review REST service access controls and audit existing user permissions as a supplementary hardening measure.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later

  1. Check the current Oracle Applications Framework version using the Oracle Applications Manager (OAM) or by querying the FND_PRODUCT_GROUPS table
  2. Review Oracle's official Critical Patch Update advisory for CVE-2024-21080 to obtain the specific patch number
  3. Apply the latest Oracle E-Business Suite 12.2.14 or later release, which includes the security fix for this vulnerability
  4. After upgrading, verify the REST Services component is functioning correctly and test the security fix
  5. Document the upgrade in the change management system
Caveat Standard Oracle E-Business Suite upgrade precautions apply - backup the database and test thoroughly in a non-production environment before applying to production

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

Fix this in Applications Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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