CVE-2024-21184
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 · uneditedVulnerability in the Oracle Database RDBMS Security component of Oracle Database Server. Supported versions that are affected are 19.3-19.23. Easily exploitable vulnerability allows high privileged attacker having Execute on SYS.XS_DIAG privilege with network access via Oracle Net to compromise Oracle Database RDBMS Security. Successful attacks of this vulnerability can result in takeover of Oracle Database RDBMS Security. 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 confidenceVulnerability in Oracle Database RDBMS Security component allows a high-privileged attacker with Execute on SYS.XS_DIAG privilege to compromise the security component via network access through Oracle Net, potentially achieving complete takeover of the RDBMS Security subsystem.
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>= 19.3, <= 19.23CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Database versionQuery the database with: SELECT version FROM v$instance; or SELECT banner FROM v$version WHERE banner LIKE 'Oracle Database%';Affected if The version is between 19.3 and 19.23 inclusive (for example, 19.3, 19.19, 19.23)
-
Check for SYS.XS_DIAG privilege grantsQuery dba_sys_privs or dba_tab_privs: SELECT grantee, privilege, owner, table_name FROM dba_sys_privs WHERE privilege = 'EXECUTE' AND owner = 'SYS' AND table_name = 'XS_DIAG';Affected if Any non-SYS users (especially high-privileged users) are granted Execute on SYS.XS_DIAG
-
Identify all users with XS_DIAG execute accessRun: SELECT grantee, owner, table_name, privilege FROM dba_tab_privs WHERE owner = 'SYS' AND table_name = 'XS_DIAG' AND privilege = 'EXECUTE';Affected if Any user besides the owner has Execute permission on XS_DIAG
-
Verify Oracle Net listener is accessibleCheck listener.ora and tnslsnr status, or query: SELECT status FROM v$listener WHERE name = 'LISTENER';Affected if The Oracle Net listener is running and accepting network connections (required for the network-based attack vector)
A user is affected if they run Oracle Database version 19.3 through 19.23 AND have the Execute on SYS.XS_DIAG privilege granted to any user beyond SYS, with network accessibility enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update addressing CVE-2024-21184 or upgrade to a patched version. Restrict and audit the SYS.XS_DIAG privilege granted to users until the patch is applied.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21184 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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