CVE-2021-2077
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 · uneditedVulnerability 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 confidenceSQL injection or similar injection vulnerability in the Shopping Cart component of Oracle iStore (E-Business Suite) allows unauthenticated remote attackers to execute arbitrary code via HTTP requests. The attack requires victim interaction (likely clicking a malicious link or submitting crafted form data), and while scoped to iStore, it may impact other E-Business Suite products due to shared components.
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>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Oracle iStore versionQuery the Oracle Applications tables (FND_APPLICATION or similar) or use Oracle Application Manager (OAM) to confirm the installed iStore version. Run: SELECT version FROM apps.fnd_product_groups WHERE application_id = (SELECT application_id FROM apps.fnd_application WHERE application_short_name = 'IBE');Affected if version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10
-
Confirm iStore HTTP endpoints are accessibleCheck web server configuration (Oracle HTTP Server/OHS or Apache) for iStore-related virtual paths (typically /OADBA/ or /ibE/ or /shop/). Verify if iStore responds on standard HTTP/HTTPS ports.Affected if iStore web endpoints are exposed externally or to untrusted networks without network filtering
-
Verify Shopping Cart module is enabledCheck Oracle iStore configuration via iStore Administrator responsibility, or query the FND_MENU_entries table to confirm the Shopping Cart (IBE_SHOPPING_CART) functionality is enabled for the affected site.Affected if Shopping Cart component is active and accessible to users/guests
-
Review HTTP access logs for SQL injection patternsExamine iStore access logs (located in $LOG_HOME or Oracle HTTP Server log directories) for suspicious request patterns in shopping cart parameters. Search for patterns like: ' UNION, ' OR '1'='1, ; DROP, and other SQL metacharacters in query strings.Affected if log analysis reveals SQL injection attempts targeting shopping cart parameters or similar anomalous SQL in HTTP requests
-
Check for recent unauthorized database changesQuery Oracle audit tables (FND_AUDIT_TRAILS, DBA_AUDIT_TRAIL) for unexpected DML or DDL operations originating from iStore application users around the time of potential exploitation. Also check for new/unexpected stored procedures or functions.Affected if audit records show unexpected database modifications or privilege escalations from iStore sessions
A system is affected if it runs Oracle iStore versions 12.1.1-12.1.3 or 12.2.3-12.2.10 with the Shopping Cart feature enabled and accessible via HTTP, and either SQL injection signatures appear in logs or unexpected database changes are detected.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2077 to all affected Oracle iStore installations (12.1.1-12.1.3 and 12.2.3-12.2.10). If immediate patching is not possible, restrict network access to iStore HTTP endpoints and monitor for suspicious shopping cart interactions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2077 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-2077 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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