dbcve.org
Product HubApplication · Oracle

CVE-2024-21252

HIGH · 8.1 CVSS v3.1 Published 2024-10-15
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 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 Product Hub product of Oracle E-Business Suite (component: Item Catalog). 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 Product Hub. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Product Hub accessible data as well as unauthorized access to critical data or complete access to all Oracle Product Hub 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 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 Product Hub contains a vulnerability in the Item Catalog component that allows a low-privileged attacker with network access via HTTP to create, delete, or modify critical data, or gain unauthorized access to data. The CVSS 3.1 score of 8.1 indicates high confidentiality and integrity impacts with no availability impact.

MitigationApply the relevant Oracle Critical Patch Update for CVE-2024-21252 to the affected Oracle Product Hub installations (versions 12.2.3-12.2.13), and restrict network access to the HTTP interface to mitigate external exploitation.

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
Product HubApplication
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
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? 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. Verify Oracle Product Hub is installed
    Check for Oracle Product Hub installation by querying the Oracle database or checking application server logs for 'Oracle Product Hub' or 'Item Catalog' components
    Affected if Oracle Product Hub is not present in the environment, the CVE does not apply
  2. Determine the installed Oracle Product Hub version
    Query the Oracle database version tables (such as fnd_product_installations or similar Oracle Applications tables) or check the Oracle E-Business Suite about page for the Product Hub version
    Affected if version is >= 12.2.3 and <= 12.2.13
  3. Confirm the Item Catalog component is enabled
    Check Oracle Product Hub configuration to verify the Item Catalog module is installed and accessible. This can be done via Oracle Application Manager or by checking the enabled product menus.
    Affected if Item Catalog component is enabled and accessible
  4. Assess network accessibility of HTTP interface
    Determine if the Oracle Product Hub HTTP ports (typically 8000-8009 or as configured) are exposed to the network. Check firewall rules, load balancer configurations, and web server settings.
    Affected if HTTP interface is externally accessible over network

User is affected if Oracle Product Hub version is between 12.2.3 and 12.2.13, the Item Catalog component is enabled, and the HTTP interface 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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply the relevant Oracle Critical Patch Update for CVE-2024-21252 to the affected Oracle Product Hub installations (versions 12.2.3-12.2.13), and restrict network access to the HTTP interface to mitigate external exploitation.

Recommended fix Moderate confidence

12.2.14 or later (apply Oracle security patch for this CPU)

  1. Contact Oracle Support to request the specific patch for CVE-2024-21252
  2. Obtain the security patch for Oracle Product Hub component (Item Catalog) from Oracle
  3. Apply the Oracle patch following Oracle's standard patching procedures for E-Business Suite
  4. Verify the patch was applied successfully by testing the Item Catalog functionality
  5. Confirm the vulnerability is resolved by reviewing Oracle's patch documentation or contacting Oracle Support
Caveat Oracle E-Business Suite patches may require downtime and should be tested in a non-production environment first

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

Fix this in Product Hub 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-21252 — 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-21252 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