Trading CommunityApplication · Oracle

CVE-2024-21167

HIGH · 8.1 CVSS v3.1 Published 2024-07-16

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 Trading Community product of Oracle E-Business Suite (component: Party Search UI). 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 Trading Community. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Trading Community accessible data as well as unauthorized access to critical data or complete access to all Oracle Trading Community 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

A vulnerability in Oracle E-Business Suite Trading Community's Party Search UI component allows low-privileged authenticated users to bypass access controls via HTTP, enabling unauthorized creation, deletion, or modification of critical data, as well as unauthorized read access to sensitive information. The vulnerability is easily exploitable over the network.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2024-21167 to Oracle E-Business Suite 12.2.3-12.2.13. Until the patch is applied, restrict network access to the Trading Community application and monitor for suspicious Party Search UI activity.

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

Trading CommunityApplication

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 installed Oracle E-Business Suite version

Query the Oracle Applications version information using the AD Administration utility, FND_APPL_TOP, or by checking the release.sql script output in the $APPL_TOP directory

Affected if The installed version falls within 12.2.3 through 12.2.13 inclusive
Confirm Trading Community module is enabled

Verify the Oracle Trading Community (TCA) module is installed and active by checking the Oracle Applications Manager or querying the ICX_PORTER table or FND_APPLICATION table for the Trading Community application

Affected if The Trading Community module is installed and running
Identify Party Search UI endpoint exposure

Review the Oracle E-Business Suite web listener configuration and HTTP server logs for access to the Party Search UI component typically hosted under the /oa_html/ or /OA_HTML/ path structure

Affected if The Party Search UI is accessible via HTTP without additional network restrictions
Audit user access to Party Search UI

Examine Oracle E-Business Suite audit tables or icx_session records to identify which users have accessed the Party Search UI functionality and their assigned responsibility levels

Affected if Low-privileged users with limited responsibilities are accessing the Party Search UI component
Review for unauthorized data modifications

Monitor Oracle Trading Community tables such as HZ_PARTIES, HZ_LOCATIONS, and HZ_ORGANIZATION_PROFILES for unexpected create, update, or delete operations by low-privileged authenticated users

Affected if Records in Trading Community tables show modifications made by users lacking appropriate business object grants

Your environment is affected if Oracle E-Business Suite version is 12.2.3 through 12.2.13, the Trading Community module is enabled, and low-privileged users can access or modify data through the Party Search UI without proper authorization checks.

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 Oracle Critical Patch Update (CPU) for CVE-2024-21167 to Oracle E-Business Suite 12.2.3-12.2.13. Until the patch is applied, restrict network access to the Trading Community application and monitor for suspicious Party Search UI activity.

Recommended fix Moderate confidence

Upgrade to a version beyond 12.2.13 (e.g., 12.2.14 or later) which would include the security fix

Check Oracle E-Business Suite Patch Set Updates (PSU) for July 2024 or the next available Critical Patch Update (CPU) that addresses CVE-2024-21167
Apply the relevant security patch for Oracle E-Business Suite 12.2.x via Oracle OPatch or the patch apply mechanism
After applying the patch, verify the fix by reviewing the patch inventory and testing the Party Search UI functionality
Confirm the patch installation completed successfully by checking the adpatch logs and running appropriate validation queries

Caveat Major version upgrades of Oracle E-Business Suite require extensive testing in a non-production environment and may require customizations to be revalidated

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

Fix this in Trading Community Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing10.0 h
Review / QA4.0 h

32.0 hours of engineering $5,580

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Notes0 Guidelines

Know something about CVE-2024-21167?

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: Trading Community

Remediation

A high-priority fix

Fix this in Trading Community 32 hrs · Moderate

Typical engagement from $5,580

Get a fix See the full breakdown ↓

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