IstoreApplication · Oracle

CVE-2021-2059

MEDIUM · 5.3 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 12.2.10 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: Web interface). 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 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

Oracle iStore web interface contains an information disclosure vulnerability allowing unauthenticated remote attackers to read a subset of accessible data via specially crafted HTTP requests. The flaw is easily exploitable over the network with only confidentiality impact (CVSS 5.3).

MitigationApply the relevant Oracle Critical Patch Update (CPU) containing the security fix for CVE-2021-2059 to the affected Oracle E-Business Suite iStore implementations (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
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. Verify Oracle iStore is installed
    Check for Oracle E-Business Suite iStore component by querying the Oracle Applications Manager interface or checking for iStore-related database objects in the APPS schema
    Affected if iStore component exists in the Oracle E-Business Suite environment
  2. Determine iStore version
    Access Oracle Applications Manager or run SQL query 'SELECT ibe_version FROM ibe_versions' against the iStore schema to obtain the installed iStore version number
    Affected if version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10 inclusive
  3. Confirm web interface is accessible
    Attempt to access the iStore storefront URL pattern (typically /iber/astore or /oa_html/ibeCCtpSplash.jsp) via HTTP from a browser or curl command
    Affected if iStore web pages are reachable over HTTP/HTTPS
  4. Check for anomalous HTTP requests in logs
    Review Oracle HTTP Server access logs or Apache access logs for unusual GET/POST requests to iStore servlets, particularly those with unexpected parameters or path traversal patterns
    Affected if suspicious or unauthorized HTTP request patterns targeting iStore endpoints are present in logs

Your environment is affected if Oracle iStore version is between 12.1.1-12.1.3 or 12.2.3-12.2.10 and the iStore web interface is accessible over the network.

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 relevant Oracle Critical Patch Update (CPU) containing the security fix for CVE-2021-2059 to the affected Oracle E-Business Suite iStore implementations (versions 12.1.1-12.1.3 and 12.2.3-12.2.10).

Fix this in Istore Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2059 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