dbcve.org
Trade ManagementApplication · Oracle

CVE-2024-21075

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: Claim Line 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

Oracle Trade Management component 'Claim Line LOV' contains an unauthenticated information disclosure vulnerability in versions 12.2.3-12.2.13 of Oracle E-Business Suite. An attacker with network access via HTTP can exploit this flaw to gain unauthorized access to sensitive data within Oracle Trade Management, with only confidentiality impact according to CVSS.

MitigationApply the applicable Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21075. Until the patch is applied, consider restricting network access to Trade Management interfaces via firewall or web application firewall rules.

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 Oracle E-Business Suite version
    Log into Oracle Applications and navigate to the 'About Oracle Applications' page, or query the FND_PRODUCT_GROUPS table. Alternatively, check the OAM (Oracle Application Manager) for version information.
    Affected if The installed version falls within the range 12.2.3 through 12.2.13 inclusive.
  2. Confirm Oracle Trade Management is installed
    Check if the Oracle Trade Management module is among the installed products. Query the FND_PRODUCT_INSTALLATIONS table or check through Oracle Application Manager.
    Affected if Oracle Trade Management is installed and running.
  3. Verify network accessibility of Trade Management web interfaces
    Check firewall rules, load balancer configurations, or WAF policies that control access to the Oracle E-Business Suite web endpoints. Determine if the /OA_HTML/ or /oracle/TM/ paths (or similar Trade Management endpoints) are exposed to untrusted networks.
    Affected if The Trade Management application is accessible over HTTP/HTTPS from untrusted network locations without proper authentication filters.
  4. Identify exposed Claim Line LOV endpoint
    Review web server configurations and reverse proxy rules to determine if the Claim Line LOV functionality (/xmlpserver/... or custom Trade Management reports/forms) is directly accessible via URL without requiring authenticated sessions.
    Affected if The Claim Line LOV component is accessible via HTTP without requiring valid authentication credentials.

A user is affected if they run Oracle E-Business Suite with Trade Management versions 12.2.3-12.2.13 and the Claim Line LOV interface is reachable over the network without authentication.

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.

From vendor data
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply the applicable Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21075. Until the patch is applied, consider restricting network access to Trade Management interfaces via firewall or web application firewall rules.

Fix this in Trade Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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