dbcve.org
IstoreApplication · Oracle

CVE-2021-2082

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: Shopping Cart). 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

Vulnerability in Oracle iStore Shopping Cart component of Oracle E-Business Suite. Unauthenticated remote attacker with network access via HTTP can exploit this flaw, requiring human interaction from a person other than the attacker. Successful attacks allow unauthorized access to critical or all accessible data, plus unauthorized update/insert/delete operations on some iStore data.

MitigationApply Oracle Critical Patch Update (CPU) for January 2021 that addresses CVE-2021-2082 in Oracle iStore; verify the patch is applicable to affected versions 12.1.1-12.1.3 and 12.2.3-12.2.10.

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. Confirm Oracle iStore is installed
    Query the Oracle E-Business Suite database for iStore presence: SELECT application_id, application_name FROM fnd_application WHERE application_name LIKE '%iStore%' OR application_name LIKE '%IBE%'; or check for iStore-related tables and packages in the database.
    Affected if No iStore installation found means not affected.
  2. Determine Oracle E-Business Suite iStore version
    Run the SQL command: SELECT patch_level FROM apps.fnd_product_installations WHERE application_id = (SELECT application_id FROM fnd_application WHERE application_short_name = 'IBE'); This shows the iStore patch level which indicates the version.
    Affected if Version falls within 12.1.1 to 12.1.3 or 12.2.3 to 12.2.10, indicating the system is vulnerable.
  3. Verify iStore web component is accessible
    Attempt to access the iStore login page via HTTP: visit https://<hostname>/OA_HTML/ibeCAcpSSOR.jsp?store=... or the standard iStore URL path /OA_HTML/ibe* on your E-Business Suite web server. Check if the application responds.
    Affected if iStore web pages are reachable without authentication, indicating the attack surface is exposed.
  4. Confirm iStore is enabled in Oracle E-Business Suite
    Check Oracle Responsibilities assigned to iStore: SELECT responsibility_name FROM fnd_responsibility WHERE responsibility_name LIKE '%iStore%' OR responsibility_name LIKE '%IBE%'; Verify the responsibility is functional and not disabled.
    Affected if iStore responsibility is active and functional, making the vulnerability exploitable.
  5. Check for existing Oracle patches
    Query applied patches: SELECT patch_name, creation_date FROM ad_bugs WHERE patch_name IN ('31720753', '31720754', '31720755', '31720756') OR description LIKE '%CVE-2021-2082%'; Check Oracle E-Business Suite patch inventory for January 2021 CPU patches.
    Affected if No relevant CVE-2021-2082 patches are applied, leaving the vulnerability unmitigated.

The environment is affected if Oracle iStore version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10, the iStore web component is accessible, and the January 2021 CPU patch for CVE-2021-2082 has not been applied.

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 Oracle Critical Patch Update (CPU) for January 2021 that addresses CVE-2021-2082 in Oracle iStore; verify the patch is applicable to affected versions 12.1.1-12.1.3 and 12.2.3-12.2.10.

Fix this in Istore Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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