dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2024-21126

MEDIUM · 5.8 CVSS v3.1 Published 2024-07-16
Fix available
A fix is available. Upgrade to after 21.14 or later.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Portable Clusterware component of Oracle Database Server. Supported versions that are affected are 19.3-19.23 and 21.3-21.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via DNS to compromise Oracle Database Portable Clusterware. While the vulnerability is in Oracle Database Portable Clusterware, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Database Portable Clusterware. CVSS 3.1 Base Score 5.8 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L).

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 Database Portable Clusterware contains a vulnerability exploitable via DNS that allows unauthenticated remote attackers to cause a partial denial of service. The attack complexity is low with no authentication required, and while the vulnerability is in the clusterware component, attacks may impact additional products due to the scope change.

MitigationApply the relevant Oracle Critical Patch Update for versions 19.3-19.23 or 21.3-21.14. Review Oracle's patch documentation for Oracle Database Portable Clusterware and test cluster stability after deployment.

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:>= 19.3, <= 19.23>= 21.3, <= 21.14

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

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

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 installation and version
    Run 'sqlplus -v' or check $ORACLE_HOME/oratab, or use 'ls -la $ORACLE_HOME' to verify installation and locate the version file
    Affected if Version is 19.3-19.23 or 21.3-21.14
  2. Confirm Portable Clusterware component is in use
    Check if Oracle Clusterware/Grid Infrastructure is installed: run 'crsctl query crs activeversion' or inspect /etc/oracle/olr.loc, or look for 'crs' processes via 'ps -ef | grep -i d.bin'
    Affected if Portable Clusterware/Grid Infrastructure binaries are present and running
  3. Verify clusterware DNS configuration exposure
    Review clusterware configuration files in $ORACLE_HOME/network/admin or Grid Infrastructure home for DNS-related settings in listener.ora, sqlnet.ora, or check 'srvctl config nodeapps' output for network configuration
    Affected if DNS-based listener registration or remote node communication is configured
  4. Check clusterware service status
    Run 'crsctl stat res -t' or 'olsnodes' to enumerate active cluster resources and nodes
    Affected if Cluster services are active, indicating the vulnerable component is exposed

If Oracle Database version falls within 19.3-19.23 or 21.3-21.14 AND Portable Clusterware/Grid Infrastructure is installed and active with DNS-based configuration, the environment is likely affected.

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
Upgrade available Upgrade to a release after 21.14
Interim mitigation

Apply the relevant Oracle Critical Patch Update for versions 19.3-19.23 or 21.3-21.14. Review Oracle's patch documentation for Oracle Database Portable Clusterware and test cluster stability after deployment.

Recommended fix Moderate confidence

Oracle 19.24+ or 21.15+ (or apply July 2024 CPU)

  1. 1. Identify the current Oracle Database Portable Clusterware version using 'crsctl query crs activeversion' or 'ls -l $ORACLE_HOME/../crs/install/oraclexe.hpi'
  2. 2. Schedule a maintenance window for the upgrade (requires downtime for cluster resources)
  3. 3. Pre-upgrade backup: Run 'mkdir -p /backup/oracle; rman target / backup database plus archivelog delete input;'
  4. 4. For 19.x affected versions (19.3-19.23): Upgrade to Oracle 19.24 or later using OPatch or Database Upgrade Assistant (DBUA)
  5. 5. For 21.x affected versions (21.3-21.14): Upgrade to Oracle 21.15 or later using OPatch or Database Upgrade Assistant (DBUA)
  6. 6. Alternatively, apply Oracle Critical Patch Update (CPU) July 2024 or later which contains the fix for CVE-2024-21126
  7. 7. After upgrade/patch, validate cluster health using 'crsctl check cluster -all' and 'srvctl status database -d <dbname>'
  8. 8. Verify the fix by checking Oracle patch inventory: 'opatch lspatches'
Caveat Oracle upgrade may require compatibility checks, review Oracle upgrade guide for required init parameters and deprecated features before proceeding

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

Fix this in Database Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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