CVE-2022-29835
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 · uneditedWD Discovery software executable files were signed with an unsafe SHA-1 hashing algorithm. An attacker could use this weakness to create forged certificate signatures due to the use of a hashing algorithm that is not collision-free. This could thereby impact the confidentiality of user content. This issue affects: Western Digital WD Discovery WD Discovery Desktop App versions prior to 4.4.396 on Mac; WD Discovery Desktop App versions prior to 4.4.396 on Windows.
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 confidenceWD Discovery software executables used SHA-1 for code signing, a cryptographically broken hash algorithm susceptible to collision attacks. An attacker could forge certificate signatures to impersonate legitimate software, potentially compromising user content confidentiality.
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< 4.4.396CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WD Discovery installationCheck if WD Discovery software is installed on the system. On Windows, open Programs and Features or check the installation directory (typically C:\Program Files\Western Digital or C:\Program Files (x86)\Western Digital). On Mac, check the /Applications folder for WD Discovery.app.Affected if WD Discovery is found installed on the system
-
Determine installed versionLocate the WD Discovery executable or application and check its version property. On Windows, right-click the executable, select Properties, and view the Details tab for File Version. On Mac, right-click WD Discovery.app, select Get Info, and view the Version field under General.Affected if The version displayed is below 4.4.396
-
Compare against affected rangeCompare the identified version number to the affected range (< 4.4.396). Ensure the full version string is evaluated (for example, 4.4.300 is below 4.4.396).Affected if The installed version number is less than 4.4.396 (for example, 4.4.300, 4.3.5, 1.0.0, etc.)
If WD Discovery is installed and its version is lower than 4.4.396, the environment is affected by the vulnerable SHA-1 code signing issue described in this CVE.
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.
dbcve · scoped4.4.396
Update WD Discovery Desktop App to version 4.4.396 or later on both Mac and Windows platforms to use secure signing algorithms.
WD Discovery Desktop App 4.4.396 or later
- Check the current version of WD Discovery Desktop App installed on the system
- Navigate to the official Western Digital website at www.westerndigital.com to download the latest version
- Download WD Discovery Desktop App version 4.4.396 or later
- Install the updated WD Discovery Desktop App version following the on-screen prompts
- Verify the installed version is 4.4.396 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29835 — 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-2022-29835 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