dbcve.org
DatabaseDatabase / datastore · Oracle

CVE-2022-21410

HIGH · 7.2 CVSS v3.1 Published 2022-04-19
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 Oracle Database - Enterprise Edition Sharding component of Oracle Database Server. The supported version that is affected is 19c. Easily exploitable vulnerability allows high privileged attacker having Create Any Procedure privilege with network access via Oracle Net to compromise Oracle Database - Enterprise Edition Sharding. Successful attacks of this vulnerability can result in takeover of Oracle Database - Enterprise Edition 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 19c Enterprise Edition Sharding component allows a high-privileged attacker with 'Create Any Procedure' privilege and network access via Oracle Net to execute arbitrary code and achieve complete takeover of the Sharding system. The low attack complexity and high impact across confidentiality, integrity, and availability make this a serious privilege escalation risk.

MitigationApply Oracle Critical Patch Update (April 2022) addressing CVE-2022-21410. Additionally, audit and restrict the 'Create Any Procedure' privilege to minimum necessary accounts, and monitor database audit logs for suspicious stored procedure creation activities.

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
DatabaseDatabase / datastore
Affected:= 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. Confirm Oracle Database 19c installation
    Query v$version or dba_registry to identify the installed Oracle Database version. Run: SELECT * FROM v$version; or SELECT version FROM dba_registry WHERE comp_id='DB';
    Affected if The installed version is any 19c release (19.x)
  2. Verify Sharding component is configured
    Check if Oracle Sharding is enabled by querying DBA_REGISTRY for the SHD component or check for gsm$* objects. Run: SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Sharding%';
    Affected if The Sharding component shows as 'VALID' or 'INSTALLED' in DBA_REGISTRY
  3. Identify users with Create Any Procedure privilege
    Query DBA_SYS_PRIVS for accounts granted the CREATE ANY PROCEDURE privilege. Run: SELECT grantee, privilege, admin_option FROM dba_sys_privs WHERE privilege='CREATE ANY PROCEDURE';
    Affected if Any user account (other than DBA roles) is listed as having CREATE ANY PROCEDURE privilege
  4. Review network access configuration
    Check Oracle Net configuration (listener.ora, sqlnet.ora) and verify what network endpoints accept connections. Inspect LISTENER_STATUS for active services and check for unauthenticated network exposure.
    Affected if Oracle Net listener accepts connections from untrusted networks without adequate restrictions

A user is affected if they run Oracle Database 19c with Sharding enabled and have any account (besides strict DBA accounts) granted the CREATE ANY Procedure privilege 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (April 2022) addressing CVE-2022-21410. Additionally, audit and restrict the 'Create Any Procedure' privilege to minimum necessary accounts, and monitor database audit logs for suspicious stored procedure creation activities.

Fix this in Database 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 help mitigating

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-2022-21410 — 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-2022-21410 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