dbcve.org
Rdbms ShardingApplication · Oracle

CVE-2021-2054

HIGH · 7.2 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 RDBMS Sharding component of Oracle Database Server. Supported versions that are affected are 12.2.0.1, 18c and 19c. Easily exploitable vulnerability allows high privileged attacker having Create Any Procedure, Create Any View, Create Any Trigger privilege with network access via Oracle Net to compromise RDBMS Sharding. Successful attacks of this vulnerability can result in takeover of RDBMS Sharding. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

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 Database RDBMS Sharding component affecting versions 12.2.0.1, 18c, and 19c. Allows high privileged attackers with Create Any Procedure, Create Any View, or Create Any Trigger privileges to compromise the sharding layer via network access, potentially achieving complete takeover of the sharded database system.

MitigationApply Oracle Critical Patch Update addressing CVE-2021-2054. Until patched, audit and restrict Create Any Procedure, Create Any View, and Create Any Trigger privileges to minimum necessary accounts.

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
Rdbms ShardingApplication
Affected:= 12.2.0.1= 18c= 19c

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 Oracle Database version
    Run: SELECT VERSION FROM V$INSTANCE; or SELECT * FROM PRODUCT_COMPONENT_VERSION;
    Affected if Version returned is 12.2.0.1, 18c, or 19c
  2. Confirm Sharding component is in use
    Check if the database is configured as a sharded environment by querying: SELECT NAME, SHARDED FROM V$DATABASE; or SELECT * FROM SHARD$;
    Affected if Database is configured with sharding enabled (SHARDED = 'Y' or entries exist in SHARD$ tables)
  3. Audit users with Create Any Procedure privilege
    Run: SELECT GRANTEE, ADMIN_OPTION FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'CREATE ANY PROCEDURE';
    Affected if Any non-admin or unnecessary accounts appear in the results
  4. Audit users with Create Any View privilege
    Run: SELECT GRANTEE, ADMIN_OPTION FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'CREATE ANY VIEW';
    Affected if Any non-admin or unnecessary accounts appear in the results
  5. Audit users with Create Any Trigger privilege
    Run: SELECT GRANTEE, ADMIN_OPTION FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'CREATE ANY TRIGGER';
    Affected if Any non-admin or unnecessary accounts appear in the results

Environment is affected if running Oracle Database 12.2.0.1, 18c, or 19c with the Sharding component enabled AND any unprivileged or non-essential accounts hold Create Any Procedure, Create Any View, or Create Any Trigger system privileges.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update addressing CVE-2021-2054. Until patched, audit and restrict Create Any Procedure, Create Any View, and Create Any Trigger privileges to minimum necessary accounts.

Fix this in Rdbms Sharding Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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