dbcve.org
CdmApplication · Rubrik

CVE-2022-30984

HIGH · 7.8 CVSS v3.1 Published 2022-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A buffer overflow vulnerability in the Rubrik Backup Service (RBS) Agent for Linux or Unix-based systems in Rubrik CDM 7.0.1, 7.0.1-p1, 7.0.1-p2 or 7.0.1-p3 before CDM 7.0.2-p2 could allow a local attacker to obtain root privileges by sending a crafted message to the RBS agent.

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

A buffer overflow vulnerability exists in the Rubrik Backup Service (RBS) Agent for Linux and Unix-based systems in Rubrik CDM versions 7.0.1 through 7.0.1-p3. A local attacker with the ability to send crafted messages to the RBS agent can exploit this buffer overflow to escalate privileges to root.

MitigationUpgrade Rubrik CDM to version 7.0.2-p2 or later to remediate this vulnerability. Since this requires local access, ensure appropriate access controls and monitoring on systems running the RBS agent.

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
CdmApplication
Affected:= 7.0.1

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

CVSS:3.1/AV:L/AC:L/PR:L/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 if Rubrik RBS Agent is installed
    Look for the Rubrik Backup Service (RBS) agent process or binaries on the system using commands like 'ps aux | grep -i rubrik', 'which rbs', or check for service files in /etc/systemd/system/ containing 'rubrik' or 'rbs'.
    Affected if The RBS agent process or binary is found running on the system.
  2. Determine the Rubrik CDM version
    Run the command to check the Rubrik CDM version - typically 'rubrik version' or check the CDM build/version file if the CLI is available. The version format appears as 7.0.1, 7.0.1-p1, 7.0.1-p2, or 7.0.1-p3.
    Affected if Unable to determine the CDM version or the version cannot be retrieved.
  3. Compare installed version against affected range
    Verify if the installed CDM version falls within the affected range: 7.0.1 through 7.0.1-p3 inclusive. This includes version 7.0.1, 7.0.1-p1, 7.0.1-p2, and 7.0.1-p3.
    Affected if The installed version is 7.0.1, 7.0.1-p1, 7.0.1-p2, or 7.0.1-p3.

A system is affected if the Rubrik RBS Agent is installed and the Rubrik CDM version is 7.0.1, 7.0.1-p1, 7.0.1-p2, or 7.0.1-p3.

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

Upgrade Rubrik CDM to version 7.0.2-p2 or later to remediate this vulnerability. Since this requires local access, ensure appropriate access controls and monitoring on systems running the RBS agent.

Recommended fix High confidence

CDM 7.0.2-p2 or later

  1. 1. Back up the current Rubrik CDM configuration and data before initiating any upgrade.
  2. 2. Download Rubrik CDM version 7.0.2-p2 or later from the official Rubrik support portal (support.rubrik.com).
  3. 3. Follow Rubrik's standard upgrade procedure for the CDM software, ensuring the RBS Agent on Linux or Unix systems is updated as part of the upgrade.
  4. 4. After upgrade completion, verify the RBS Agent version is 7.0.2-p2 or later by checking the agent's version information.
  5. 5. Test that the RBS Agent is functioning normally and validate that the vulnerability is no longer present.

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

Fix this in Cdm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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