CVE-2019-11551
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 · uneditedIn Code42 Enterprise and Crashplan for Small Business through Client version 6.9.1, an attacker can craft a restore request to restore a file through the Code42 app to a location they do not have privileges to write.
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 confidenceCode42 Enterprise and Crashplan for Small Business Client versions through 6.9.1 contain a vulnerability where authenticated users can craft restore requests to write files to locations on the file system where they lack proper write privileges, potentially allowing privilege escalation or arbitrary file placement.
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<= 6.9.1<= 6.9.1CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Code42 or Crashplan client versionOn Windows, open Add or Remove Programs and locate Code42 or Crashplan entry, then view the installed version. Alternatively, right-click the client executable (Code42.exe or Crashplan.exe), select Properties, and check the Details tab for File Version.Affected if The displayed version is 6.9.1 or any lower version number.
-
Confirm client executable version via command lineOpen Command Prompt and run: dir "C:\Program Files\Code42\Code42.exe" /s 2>nul or dir "C:\Program Files\Crashplan\Crashplan.exe" /s 2>nul. Then run: (path to exe) -version or check version info with PowerShell: (Get-Item "(path)").VersionInfo.FileVersionAffected if The returned version string shows 6.9.1 or below.
-
Verify authenticated user access to client restore featureLog into the Code42 or Crashplan client with a standard user account. Navigate to the Restore or Backup tab to confirm the restore functionality is accessible and not disabled by administrator policy.Affected if An authenticated non-admin user can access and initiate restore operations.
-
Check restore destination configurationExamine the client configuration file (typically under AppData\Local\Code42 or AppData\Local\Crashplan) for restore path settings. Look for any configuration that restricts allowed restore destination directories.Affected if No restrictive path policies are configured, allowing arbitrary restore destinations.
You are affected if the installed Code42 or Crashplan client version is 6.9.1 or lower and authenticated users have access to the restore functionality without restrictive path controls.
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.
From vendor dataUpgrade Code42/Crashplan client to a version beyond 6.9.1 as provided by vendor patches, and restrict restore destination paths in the application configuration to prevent abuse.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11551 — 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-2019-11551 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