dbcve.org
Data Domain Operating SystemOperating system · Dell

CVE-2025-43914

HIGH · 7.8 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 7.10.1.70 / 8.3.1.10 or later.
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
Dell PowerProtect Data Domain BoostFS for Linux Ubuntu systems of Feature Release versions 7.7.1.0 through 8.3.0.15, LTS2025 release version 8.3.1.0, LTS2024 release versions 7.13.1.0 through 7.13.1.30, LTS 2023 release versions 7.10.1.0 through 7.10.1.60, contain an Incorrect Privilege Assignment vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Unauthorized access.

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 · moderate confidence

Dell PowerProtect Data Domain BoostFS for Ubuntu Linux contains an Incorrect Privilege Assignment vulnerability where low-privileged local attackers can exploit improper privilege configuration to gain unauthorized access to the system. This is a local privilege escalation issue affecting specific Feature Release and LTS versions.

MitigationApply vendor-provided security patches for the affected PowerProtect Data Domain BoostFS versions (7.7.1.0-8.3.0.15, 7.10.1.0-7.10.1.60, 7.13.1.0-7.13.1.30, 8.3.1.0) as specified in Dell Security Advisory. If no patch is available, restrict local access to trusted users and review file/system permissions for BoostFS components.

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
Data Domain Operating SystemOperating system
Affected:>= 7.7.1.0, < 7.10.1.70>= 7.13.1.0, <= 7.13.1.40>= 8.0.0.0, <= 8.3.0.15>= 8.3.1.0, < 8.3.1.10

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. Verify if PowerProtect Data Domain BoostFS is installed
    Run 'dpkg -l | grep -i boostfs' or 'ls -la /opt/dell/boostfs' or check for the boostfs service via 'systemctl list-units | grep -i boostfs'
    Affected if BoostFS package or directory is found on the system
  2. Determine installed BoostFS version
    Run 'dpkg -l | grep -i boostfs' to get the package version, or check '/opt/dell/boostfs/version' if it exists
    Affected if The version falls within any of these ranges: 7.7.1.0 to 7.10.1.69, 7.13.1.0 to 7.13.1.40, 8.0.0.0 to 8.3.0.15, or 8.3.1.0 to 8.3.1.9
  3. Identify BoostFS binaries and scripts
    Search for BoostFS executables with 'find / -name "*boostfs*" -type f 2>/dev/null' or check common paths like /opt/dell/boostfs/bin/, /usr/local/boostfs/bin/
    Affected if BoostFS binaries exist on the system and version is in affected range
  4. Check file permissions on BoostFS components
    Run 'ls -la' on BoostFS installation directories and binaries to identify world-writable or group-writable files, or SUID/SGID binaries owned by privileged users
    Affected if Any BoostFS binary or script has overly permissive ownership or permissions (such as SUID bits, world-writable permissions, or ownership by root without appropriate restrictions)
  5. Verify Ubuntu OS version
    Run 'cat /etc/lsb-release' or 'cat /etc/os-release' to confirm the Ubuntu version
    Affected if System is running Ubuntu Linux with BoostFS installed and version is affected

A system is affected if PowerProtect Data Domain BoostFS for Ubuntu Linux is installed and the installed version falls within the affected ranges (7.7.1.0-7.10.1.69, 7.13.1.0-7.13.1.40, 8.0.0.0-8.3.0.15, or 8.3.1.0-8.3.1.9), as this enables the improper privilege configuration that allows local privilege escalation.

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.

From vendor data
Upgrade available Upgrade to 7.10.1.70 / 8.3.1.10 or later
Fixed in 7.10.1.708.3.1.10
Interim mitigation

Apply vendor-provided security patches for the affected PowerProtect Data Domain BoostFS versions (7.7.1.0-8.3.0.15, 7.10.1.0-7.10.1.60, 7.13.1.0-7.13.1.30, 8.3.1.0) as specified in Dell Security Advisory. If no patch is available, restrict local access to trusted users and review file/system permissions for BoostFS components.

Fix this in Data Domain Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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