dbcve.org
IstoreApplication · Oracle

CVE-2024-21143

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
62/100
Remediation priority · Elevated
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 iStore product of Oracle E-Business Suite (component: User Management). 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 iStore. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle iStore accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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

Information disclosure vulnerability in Oracle iStore User Management component allowing unauthenticated remote attackers with network access to read a subset of accessible data via HTTP. Low attack complexity with no authentication required but limited to confidentiality-only impact.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2024-21143; if patching is delayed, restrict network access to Oracle iStore HTTP endpoints via network segmentation or WAF 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
IstoreApplication
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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Confirm Oracle iStore is installed
    Check for iStore components in Oracle E-Business Suite by querying the Oracle Applications tables, or look for iStore-related Oracle homes and application directories on the application server.
    Affected if iStore is not present in the environment, the system is not affected.
  2. Identify the installed iStore version
    Query the Oracle Applications version tables (e.g., FND_PRODUCT_GROUPS or similar release information tables) or check the iStore patch level via Oracle OPatch if available. Compare the version number to the affected range of >= 12.2.3 and <= 12.2.13.
    Affected if The installed version falls within 12.2.3 through 12.2.13, proceed to next check.
  3. Verify the iStore HTTP interface is enabled
    Check the Oracle E-Business Suite configuration for iStore HTTP server listener status. In Oracle E-Business Suite, verify whether the iStore module is enabled in Oracle Application Manager (OAM) or through the context file settings (specifically the s_web_ssl_enabled or similar iStore configuration entries).
    Affected if iStore HTTP interface is disabled or the iStore module is not enabled, the specific flaw pathway may not be exposed.
  4. Assess network exposure of iStore endpoints
    Review network access controls, load balancer rules, or firewall policies to determine if iStore URLs (typically under /ibefore/ or /oa_weboam/ibe) are reachable from untrusted networks. Check if the HTTP listener port is exposed externally.
    Affected if iStore HTTP endpoints are reachable from untrusted network segments without authentication, the vulnerability is exploitable in practice.

The environment is affected if Oracle iStore version 12.2.3 through 12.2.13 is installed with the HTTP interface enabled and accessible from network locations where unauthenticated attackers could send HTTP requests.

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 Oracle Critical Patch Update (CPU) for CVE-2024-21143; if patching is delayed, restrict network access to Oracle iStore HTTP endpoints via network segmentation or WAF rules.

Fix this in Istore Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
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,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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