dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2021-2332

MEDIUM · 6.7 CVSS v3.1 Published 2021-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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 Oracle LogMiner component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1 and 19c. Easily exploitable vulnerability allows high privileged attacker having DBA privilege with network access via Oracle Net to compromise Oracle LogMiner. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle LogMiner accessible data as well as unauthorized read access to a subset of Oracle LogMiner accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle LogMiner. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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

Oracle LogMiner vulnerability allowing a high-privileged attacker with DBA privileges and network access via Oracle Net to create, delete, or modify critical data, read a subset of accessible data, or cause denial of service through hangs or crashes in the Oracle LogMiner component.

MitigationApply the Oracle Critical Patch Update (CPU) for July 2021 that addresses CVE-2021-2332, or upgrade to a patched version of Oracle Database 12.1.0.2, 12.2.0.1, or 19c.

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
Database ServerDatabase / datastore
Affected:= 12.1.0.2= 12.2.0.1= 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
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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
    Connect to the database as SYSDBA and run: SELECT VERSION FROM V$INSTANCE; or check the oratab/Oracle inventory for installed version
    Affected if Version matches 12.1.0.2, 12.2.0.1, or 19c exactly (no patch applied)
  2. Confirm LogMiner component is present
    Query: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%LogMiner%';
    Affected if LogMiner component is installed and accessible (STATUS = 'VALID')
  3. Verify DBA privileges exist in the environment
    Query: SELECT GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTED_ROLE = 'DBA'; or check for users with DBA role granted
    Affected if Any user accounts have DBA privileges, creating the attack surface for the high-privileged attacker scenario
  4. Check Oracle Net listener status and accessibility
    Run: lsnrctl status LISTENER (or check listener.ora for configured listeners)
    Affected if Oracle Net listener is running and accepting network connections, enabling remote attack vector

Environment is affected if running unpatched Oracle Database 12.1.0.2, 12.2.0.1, or 19c with LogMiner available and DBA privileges 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.

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

Apply the Oracle Critical Patch Update (CPU) for July 2021 that addresses CVE-2021-2332, or upgrade to a patched version of Oracle Database 12.1.0.2, 12.2.0.1, or 19c.

Recommended fix Moderate confidence

Apply the relevant Oracle Critical Patch Update (July 2021 CPU or later) containing the fix for CVE-2021-2332

  1. 1. Identify the Oracle Critical Patch Update (CPU) that contains the fix for CVE-2021-2332 by checking the Oracle Critical Patch Updates advisory for July 2021 or subsequent CPUs.
  2. 2. Access My Oracle Support (support.oracle.com) and search for CVE-2021-2332 to obtain the specific patch numbers for your affected versions (12.1.0.2, 12.2.0.1, 19c).
  3. 3. Download the applicable patch(es) from My Oracle Support using your Oracle Support credentials.
  4. 4. Apply the patch using OPatch: Navigate to the Oracle Home directory and run 'opatch apply' with the downloaded patch directory.
  5. 5. Alternatively for 19c, apply the patch using DBMS_QOPATCH procedures or via Oracle Enterprise Manager if configured.
  6. 6. After applying, verify the patch status by running 'opatch lspatches' to confirm CVE-2021-2332 is listed as patched.
  7. 7. Restart the Oracle Database instance and associated services as required by the patch application.
Caveat Patches are generally non-breaking but require downtime for application; always test in non-production first and review the README.txt for any specific prerequisites or post-install steps

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

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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