dbcve.org
DatabaseDatabase / datastore · Oracle

CVE-2022-21411

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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 Gateway / Generic ODBC Connectivity component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 19c and 21c. Easily exploitable vulnerability allows low privileged attacker having Create Session privilege with network access via Oracle Net to compromise RDBMS Gateway / Generic ODBC Connectivity. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of RDBMS Gateway / Generic ODBC Connectivity accessible data as well as unauthorized read access to a subset of RDBMS Gateway / Generic ODBC Connectivity accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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

This is an Oracle Database vulnerability in the RDBMS Gateway/Generic ODBC Connectivity component, which allows Oracle to query non-Oracle databases via ODBC. A low-privileged attacker with Create Session privilege and network access via Oracle Net can exploit this to gain unauthorized read and write access to a subset of accessible data through the gateway.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2022-21411 for the affected versions (12.1.0.2, 19c, 21c). If immediate patching is not feasible, restrict network access to the Oracle Net listener and limit Create Session privilege to only required users.

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:= 12.1.0.2= 19c= 21c

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Identify Oracle Database version
    Run the query: SELECT VERSION FROM V$INSTANCE; or check the oracle inventory for the installed database version.
    Affected if The version returned is 12.1.0.2, 19c, or 21c.
  2. Confirm Gateway/ODBC component is installed
    Query DBA_REGISTRY or check for installed components: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Gateway%' OR COMP_NAME LIKE '%ODBC%';
    Affected if The Gateway/Generic ODBC Connectivity component is present and valid in the registry.
  3. Verify Oracle Net listener is accessible
    Check if the Oracle Net listener (TNS Listener) is running and accepting connections: lsnrctl status LISTENER (or check listener.ora and sqlnet.ora for network exposure).
    Affected if The Oracle Net listener is running and accessible from the network, allowing external connections.
  4. Check for users with Create Session privilege
    Query for users granted Create Session: SELECT GRANTEE FROM DBA_SYS_PRIVS WHERE PRIVILEGE='CREATE SESSION';
    Affected if There are non-admin users (other than SYS, SYSTEM) granted Create Session privilege, especially over the network.

All four conditions must be true for the environment to be affected: the database version is 12.1.0.2, 19c, or 21c; the Gateway/ODBC component is installed; the Oracle Net listener is network-accessible; and low-privileged users with Create Session exist.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2022-21411 for the affected versions (12.1.0.2, 19c, 21c). If immediate patching is not feasible, restrict network access to the Oracle Net listener and limit Create Session privilege to only required users.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) April 2022 or later

  1. 1. Check Oracle Critical Patch Update (CPU) advisory for April 2022 for CVE-2022-21411
  2. 2. Navigate to My Oracle Support (support.oracle.com) and search for patch availability for your specific Oracle Database version (12.1.0.2, 19c, or 21c)
  3. 3. Apply the appropriate Oracle Critical Patch Update that addresses this vulnerability
  4. 4. After patching, verify the RDBMS Gateway / Generic ODBC Connectivity component is updated by checking the patch applied successfully
Caveat Oracle patches typically require downtime for application; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Database Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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