dbcve.org
Enc DatavaultApplication · Zendesk

CVE-2021-36750

HIGH · 8.1 CVSS v3.1 Published 2021-12-22
Fix available
A fix is available. Upgrade to 7.2 / 67.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
ENC DataVault before 7.2 and VaultAPI v67 mishandle key derivation, making it easier for attackers to determine the passwords of all DataVault users (across USB drives sold under multiple brand names).

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

The vulnerability lies in the key derivation implementation of ENC DataVault (before v7.2) and VaultAPI (before v67) encryption software. Weak or improper key derivation allows attackers to more easily determine user passwords for encrypted USB drives, affecting products sold under multiple brand names.

MitigationUpgrade to DataVault 7.2 or VaultAPI v67 or later to obtain the corrected key derivation implementation. Users should consider changing passwords on existing volumes after updating.

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
Enc DatavaultApplication
Affected:< 7.2
Enc VaultapiApplication
Affected:< 67.0
SecureaccessApplication
Affected:= 3.02

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

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

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 the installed encryption product
    Determine which encryption software is in use: ENC DataVault, VaultAPI, or Sandisk SecureAccess. Check the application name in Programs and Features, the software itself, or the USB drive vendor software.
    Affected if The product is DataVault, VaultAPI, or Sandisk SecureAccess.
  2. Check the installed version of the encryption software
    Locate the version information within the application (typically via Help > About or the main window), or check the installed program details in the system. Compare this version number against the affected ranges.
    Affected if Version cannot be determined or is below the patched release.
  3. Verify DataVault version if applicable
    If using Zendesk Enc DataVault, confirm the exact version number is less than 7.2.
    Affected if DataVault version is present and is less than 7.2.
  4. Verify VaultAPI version if applicable
    If using VaultAPI, confirm the exact version number is less than 67.0.
    Affected if VaultAPI version is present and is less than 67.0.
  5. Verify Sandisk SecureAccess version if applicable
    If using Sandisk SecureAccess, confirm the exact version number is 3.02.
    Affected if Sandisk SecureAccess version is exactly 3.02.

The environment is affected if DataVault < 7.2, VaultAPI < 67.0, or Sandisk SecureAccess = 3.02 is installed and being used to encrypt or protect volumes.

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 7.2 / 67.0 or later
Fixed in 7.267.0
Interim mitigation

Upgrade to DataVault 7.2 or VaultAPI v67 or later to obtain the corrected key derivation implementation. Users should consider changing passwords on existing volumes after updating.

Recommended fix Moderate confidence

ENC DataVault 7.2 or later; VaultAPI 67.0 or later; Secureaccess - vendor clarification needed

  1. 1. Identify the specific ENC DataVault software version currently installed by checking the application's About or Help section
  2. 2. Identify the VaultAPI version in use by checking the software documentation or system configuration
  3. 3. For ENC DataVault: Download and install version 7.2 or later from the vendor's official website (encsecurity.com or westerndigital.com)
  4. 4. For VaultAPI: Upgrade to version 67.0 or later from the official vendor source
  5. 5. For Secureaccess: Contact ENC Security directly to confirm the correct fixed version, as only version 3.02 is listed as affected
  6. 6. After upgrading, verify that the key derivation function properly implements rate limiting or account lockout to prevent brute force attacks
  7. 7. Consider resetting all user passwords as a precautionary measure given the vulnerability allows password determination
Caveat Before upgrading, review release notes for any changes to encryption formats or password recovery processes that may affect data access

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

Fix this in Enc Datavault Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
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,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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