dbcve.org
IstoreApplication · Oracle

CVE-2021-2096

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 allowing unauthenticated network attacker via HTTP to access critical data or perform unauthorized DML operations. Requires human interaction (UI:R) and while primarily affecting iStore, attacks may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Update (January 2021 or later) for Oracle E-Business Suite addressing iStore. Implement compensating controls: network segmentation, WAF rules, and monitor for suspicious shopping cart activity until patch is applied.

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 E-Business Suite installation
    Query the database for E-Business Suite version: SELECT version FROM apps.fnd_product_groups; or check the Oracle Applications context file (context_name.xml) in $INST_TOP/admin or $APPL_TOP/admin/
    Affected if E-Business Suite is installed and version matches 12.1.x or 12.2.x
  2. Verify iStore module is enabled
    Check iStore responsibility assignment: Query SELECT * FROM fnd_responsibility WHERE responsibility_name LIKE '%iStore%'; or check via Oracle Applications Manager (OAM) console under iStore administration.
    Affected if iStore responsibility is assigned and the module is accessible via Oracle Applications
  3. Check installed iStore version
    Query: SELECT patch_level FROM fnd_product_installations WHERE product='IBE'; or check the iStore patch level in Oracle Applications Manager under the iStore module details.
    Affected if Version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10 inclusive
  4. Confirm HTTP access to iStore is enabled
    Check Oracle HTTP Server (OHS) configuration for iStore mod_ossl or check the iStore URL is accessible: Access https://<host>/otg/ or /ibE store front. Review jserv.properties or httpd.conf for iStore servlet mappings.
    Affected if iStore is accessible over HTTP/HTTPS without authentication bypass restrictions in place
  5. Review for suspicious shopping cart activity
    Check iStore audit logs and database for unusual shopping cart operations: SELECT * FROM ibe_cart_hdr WHERE creation_date > recent AND (user_name IS NULL OR ip_address IS UNEXPECTED); Review access logs for high-volume cart creation from single IP.
    Affected if Unusual cart creation patterns or unauthorized DML operations are observed in logs

User is affected if Oracle E-Business Suite with iStore is installed, the version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10, and iStore is accessible over HTTP.

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 (January 2021 or later) for Oracle E-Business Suite addressing iStore. Implement compensating controls: network segmentation, WAF rules, and monitor for suspicious shopping cart activity until patch is applied.

Fix this in Istore 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-2021-2096 — 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-2096 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