dbcve.org
Trade ManagementApplication · Oracle

CVE-2024-21076

HIGH · 7.5 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Trade Management product of Oracle E-Business Suite (component: Offer LOV). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Trade Management. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Trade Management accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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

Unauthenticated HTTP-based vulnerability in the Offer LOV (List of Values) component of Oracle Trade Management (part of Oracle E-Business Suite). Attackers with network access can exploit this to gain unauthorized access to sensitive data without any credentials, as indicated by the CVSS vector showing no authentication required (PR:N) and high confidentiality impact.

MitigationApply the relevant Oracle Critical Patch Update (CPU) containing the fix for this vulnerability to Oracle Trade Management versions 12.2.3-12.2.13. Additionally, restrict network access to Oracle E-Business Suite interfaces using network segmentation or Web Application Firewall as a compensating control until the patch can be 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
Trade ManagementApplication
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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 if Oracle Trade Management is installed
    Locate the Oracle E-Business Suite installation directory and check for the Trade Management module. Look for the 'Oracle Trading Management' or 'Oracle Trade Management' directory structure, typically under the EBS_BASE/applications directory.
    Affected if Oracle Trade Management module exists in the Oracle E-Business Suite environment
  2. Determine the installed version of Oracle Trade Management
    Query the Oracle EBS version information. This can typically be found in the context file, Oracle Applications Manager (OAM), or by running SQL query 'SELECT version FROM apl_version WHERE product = 'TRADE'' against the APPS schema.
    Affected if The installed version is between 12.2.3 and 12.2.13 inclusive (>= 12.2.3 AND <= 12.2.13)
  3. Verify HTTP accessibility of the Offer LOV component
    Check the Oracle E-Business Suite web listener configuration (OHS/Oracle HTTP Server or Apache) to confirm the /offers/lov or similar Offer LOV endpoint is accessible via HTTP/HTTPS. Review the mod_plsql configuration or REST endpoint definitions.
    Affected if The Offer LOV web interface is exposed and accessible over HTTP or HTTPS without requiring authentication
  4. Confirm network exposure of the EBS interfaces
    Review network configuration, firewall rules, and load balancer settings to determine if the Oracle E-Business Suite applications tier is accessible from untrusted networks. Check if port 8000, 8001, or the configured web listener ports are open to the network where attackers could originate requests.
    Affected if The EBS web interfaces (including Trade Management) are reachable from network segments without proper access controls

A system is affected if Oracle Trade Management version 12.2.3 through 12.2.13 is installed and its Offer LOV component is accessible over HTTP from the network without authentication requirements.

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 (CPU) containing the fix for this vulnerability to Oracle Trade Management versions 12.2.3-12.2.13. Additionally, restrict network access to Oracle E-Business Suite interfaces using network segmentation or Web Application Firewall as a compensating control until the patch can be applied.

Recommended fix High confidence

Oracle Trade Management 12.2.14 or later (or apply April 2024 CPU or later)

  1. 1. Review the Oracle Critical Patch Update (CPU) for April 2024 or later, which contains the fix for CVE-2024-21076
  2. 2. Download and apply the relevant Oracle E-Business Suite security patch from My Oracle Support (MOS) for the Trade Management module
  3. 3. Alternatively, upgrade Oracle Trade Management to version 12.2.14 or higher which contains the security fix
  4. 4. After applying the patch or upgrade, verify that the Offer LOV component no longer allows unauthenticated access
  5. 5. Test the fix in a non-production environment before deploying to production
Caveat Oracle E-Business Suite patches may require downtime and thorough testing; ensure backup and rollback plan are in place before applying

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

Fix this in Trade Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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