dbcve.org
IstoreApplication · Oracle

CVE-2021-2089

HIGH · 8.2 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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: Runtime Catalog). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle iStore. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle iStore, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle iStore accessible data as well as unauthorized update, insert or delete access to some of Oracle iStore accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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

Unauthenticated remote vulnerability in Oracle iStore's Runtime Catalog component allows attackers via HTTP to access critical data or perform unauthorized updates/inserts/deletes to some Oracle iStore data. The attack requires human interaction (UI:R) and while targeting Oracle iStore, may impact additional products in the E-Business Suite.

MitigationApply the Oracle Critical Patch Update (CPU) addressing CVE-2021-2089. Until patched, restrict network access to Oracle iStore HTTP endpoints and implement additional authentication controls on affected endpoints.

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.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10

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
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 if Oracle iStore is installed
    Query the Oracle E-Business Suite application registry or check for iStore module presence using the Oracle Applications Manager (OAM) or by querying the FND_PRODUCT_INSTALLATIONS table
    Affected if Oracle iStore module is present in the environment
  2. Determine the installed Oracle iStore version
    Check the iStore version through Oracle E-Business Suite diagnostics or by querying the version information in the iStore administration interface
    Affected if Version is 12.1.1 through 12.1.3, or 12.2.3 through 12.2.10
  3. Verify Runtime Catalog component is accessible
    Confirm the Runtime Catalog feature is enabled in iStore by checking the iStore configuration settings or by accessing the /OA_HTML/ibeCDscCmpnt.jsp or similar Runtime Catalog endpoints
    Affected if Runtime Catalog component is enabled and accessible via HTTP
  4. Check HTTP endpoint exposure
    Determine if iStore HTTP endpoints are exposed to network access, particularly the Runtime Catalog functionality accessible via web browser
    Affected if iStore HTTP endpoints are externally accessible without additional authentication controls

Your environment is affected if Oracle iStore version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10 AND the Runtime Catalog component is enabled and accessible via HTTP, since the vulnerability allows unauthenticated HTTP-based access to data through that component.

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.10
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) addressing CVE-2021-2089. Until patched, restrict network access to Oracle iStore HTTP endpoints and implement additional authentication controls on affected endpoints.

Fix this in Istore Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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