dbcve.org
Trade ManagementApplication · Oracle

CVE-2024-21077

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: GL Accounts 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

This is an unauthenticated information disclosure vulnerability in Oracle Trade Management's GL Accounts LOV (List of Values) component within Oracle E-Business Suite versions 12.2.3-12.2.13. An attacker with network access via HTTP can exploit this to gain unauthorized access to sensitive data, with high confidentiality impact but no integrity or availability impact according to the CVSS 3.1 vector.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21077, or implement compensating controls such as network segmentation and Web Application Firewall (WAF) rules if immediate patching is not feasible.

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 installation
    Locate the E-Business Suite installation directory or check for Oracle application server processes listening on standard HTTP/HTTPS ports (typically 8000-8009 or 443/80). Query the Oracle database for the current application version using SELECT release_name FROM apps.fnd_product_groups; or check the OA_DIRECTORY / PATH environment variables.
    Affected if Oracle E-Business Suite is not found or the version cannot be determined
  2. Verify Oracle Trade Management module is installed
    Check if the Trade Management module is part of the installed modules. Query the Oracle database: SELECT application_name, application_id FROM fnd_application WHERE application_name LIKE '%Trade%'; or check for the presence of trading-related tableschemas in the database.
    Affected if Oracle Trade Management module is not installed or cannot be confirmed
  3. Determine the exact E-Business Suite version
    Query the version from the database using: SELECT release_name, patch_level FROM fnd_product_groups WHERE application_id = 800; (Application ID 800 is typically the core EBS ID). Alternatively, access the Oracle Applications Manager (OAM) dashboard or check the $APPLTOP/ADMIN/sql directory for version files.
    Affected if The version falls within the range 12.2.3 through 12.2.13 inclusive
  4. Confirm GL Accounts LOV component accessibility
    Attempt to access the GL Accounts List of Values page through the Trade Management module. The typical path follows the pattern: /OA_HTML/zzz where zzz is the LOV function. Check web server access logs for requests to Trade Management LOV functions.
    Affected if The GL Accounts LOV component is accessible without authentication and responds to HTTP requests

The environment is affected if Oracle E-Business Suite version 12.2.3 through 12.2.13 is running with the Oracle Trade Management module and its GL Accounts LOV component is network-accessible.

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 relevant Oracle Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21077, or implement compensating controls such as network segmentation and Web Application Firewall (WAF) rules if immediate patching is not feasible.

Fix this in Trade Management 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-21077 — 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-21077 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