dbcve.org
Cloud Data ManagementApplication · Rubrik

CVE-2024-36068

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-27
Fix available
A fix is available. Upgrade to 8.1.3 / 9.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An incorrect access control vulnerability in Rubrik CDM versions prior to 9.1.2-p1, 9.0.3-p6 and 8.1.3-p12, allows an attacker with network access to execute arbitrary code.

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

Rubrik CDM contains an incorrect access control vulnerability in versions prior to 9.1.2-p1, 9.0.3-p6, and 8.1.3-p12. An attacker with network access to the affected system can bypass access controls and execute arbitrary code, resulting in full system compromise.

MitigationUpgrade Rubrik CDM to version 9.1.2-p1, 9.0.3-p6, or 8.1.3-p12 or later. Restrict network access to management interfaces until patches are applied.

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
Cloud Data ManagementApplication
Affected:< 8.1.3>= 9.0.0, < 9.0.3>= 9.1.0, < 9.1.2= 8.1.3= 9.0.3= 9.1.2

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Rubrik CDM version via CLI
    Log into the Rubrik cluster via SSH as admin and run: `rubrik version` or `system info`
    Affected if The version displayed is less than 8.1.3, or is 8.1.3 without patch 12, or is between 9.0.0 and 9.0.3 without patch 6, or is between 9.1.0 and 9.1.2 without patch 1
  2. Check version via web UI
    Access the Rubrik CDM web UI, navigate to the cluster settings or about page, and locate the version information displayed there
    Affected if The displayed version falls within any of the vulnerable ranges listed in the CVE (see step 1)
  3. Verify patch level if version matches a vulnerable release
    If the base version is 8.1.3, 9.0.3, or 9.1.2, check whether the patch level is p12, p6, or p1 or higher respectively
    Affected if The patch level is below p12 for 8.1.3, below p6 for 9.0.3, or below p1 for 9.1.2
  4. Confirm network exposure of management interface
    Review firewall rules or network segmentation configuration to determine if the Rubrik management interface (typically ports 443, 22) is accessible from untrusted networks
    Affected if The management interface is exposed to the internet or untrusted internal networks without proper access restrictions

The environment is affected if the installed Rubrik CDM version is prior to 8.1.3-p12, 9.0.3-p6, or 9.1.2-p1 AND the management interface is network-accessible to an attacker.

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 8.1.3 / 9.0.3 / 9.1.2 or later
Fixed in 8.1.39.0.39.1.2
Interim mitigation

Upgrade Rubrik CDM to version 9.1.2-p1, 9.0.3-p6, or 8.1.3-p12 or later. Restrict network access to management interfaces until patches are applied.

Recommended fix High confidence

Upgrade to 8.1.3-p12 (for 8.1.x branch), 9.0.3-p6 (for 9.0.x branch), or 9.1.2-p1 (for 9.1.x branch) - select the appropriate patch based on your current version branch

  1. 1. Identify the current Rubrik CDM version by accessing the Rubrik cluster UI or using the CLI command: rubrik cluster version
  2. 2. Determine which version branch is currently deployed (8.1.x, 9.0.x, or 9.1.x)
  3. 3. For clusters on version 8.1.x: Upgrade to version 8.1.3-p12 or later
  4. 4. For clusters on version 9.0.x: Upgrade to version 9.0.3-p6 or later
  5. 5. For clusters on version 9.1.x: Upgrade to version 9.1.2-p1 or later
  6. 6. Review the Rubrik upgrade documentation and release notes for any pre-upgrade requirements
  7. 7. Create a snapshot or backup of the current configuration
  8. 8. Schedule the upgrade during a planned maintenance window
Caveat Check Rubrik release notes for any compatibility considerations or known issues before upgrading; major version upgrades may have feature or API changes

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

Fix this in Cloud Data Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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