dbcve.org
CrashplanApplication · Code42

CVE-2017-9830

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Remote Code Execution is possible in Code42 CrashPlan 5.4.x via the org.apache.commons.ssl.rmi.DateRMI Java class, because (upon instantiation) it creates an RMI server that listens on a TCP port and deserializes objects sent by TCP clients.

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

Code42 CrashPlan 5.4.x contains a Java deserialization vulnerability in the org.apache.commons.ssl.rmi.DateRMI class. Upon instantiation, this class automatically creates an RMI server listening on a TCP port that deserializes objects from incoming TCP connections without validating the objects, allowing remote unauthenticated attackers to inject and execute arbitrary Java code.

MitigationUpgrade to a patched version of Code42 CrashPlan that addresses this vulnerability. If immediate patching is not possible, restrict network access to the RMI port using firewall rules or disable the RMI service if not required for operation.

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
CrashplanApplication
Affected:= 5.4

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

CVSS:3.0/AV:N/AC:L/PR:N/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 Code42 CrashPlan is installed
    Check for Code42 CrashPlan installation directory (common paths: C:\Program Files\Code42 CrashPlan on Windows, /Applications/Code42 CrashPlan.app on Mac, /opt/code42/crashplan on Linux) or look for the service process running
    Affected if Code42 CrashPlan software is found on the system
  2. Determine installed CrashPlan version
    Locate the version file or check the service properties. On Windows, check the uninstall entry in registry or look for version.info in the install directory. On Linux/Mac, check the conf/version.conf file or run: sudo service crashplan status
    Affected if Version is 5.4.x (specifically 5.4)
  3. Identify if RMI service is running and listening
    Run netstat or ss command to check for listening TCP ports associated with CrashPlan. Look for ports in the common RMI range (1099, or dynamic ports). Example: netstat -anp | grep -i crashplan or Get-Process -Name CrashPlan* | ForEach-Object { Get-NetTCPConnection -OwningProcess $_.Id -State Listen }
    Affected if A TCP port is open and listening for RMI connections by the CrashPlan process
  4. Check RMI port exposure to network
    Verify if the listening RMI port is bound to all interfaces (0.0.0.0) rather than localhost only. Use: netstat -an | grep <port> to examine the local address binding
    Affected if The RMI port is bound to 0.0.0.0 or an external IP, making it network-accessible rather than localhost-only

You are affected if Code42 CrashPlan version 5.4 is installed and the RMI service is exposed on a listening TCP port accessible from the network.

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 to a patched version of Code42 CrashPlan that addresses this vulnerability. If immediate patching is not possible, restrict network access to the RMI port using firewall rules or disable the RMI service if not required for operation.

Recommended fix Moderate confidence

Latest Code42 CrashPlan version (5.5 or higher, check with Code42 for current stable release)

  1. 1. Back up all CrashPlan data and configurations before proceeding with any upgrade.
  2. 2. Download the latest version of Code42 CrashPlan from the official Code42 website (code42.com) or your designated update channel.
  3. 3. Verify the integrity of the downloaded installer using checksums if provided by Code42.
  4. 4. Stop the CrashPlan service on all affected systems.
  5. 5. Install the newer version of CrashPlan that addresses CVE-2017-9830.
  6. 6. Restart the CrashPlan service.
  7. 7. Verify that the DateRMI service is no longer exposed or that the vulnerability is patched by confirming the org.apache.commons.ssl.rmi.DateRMI class is no longer creating an unauthenticated RMI listener.
  8. 8. Test normal CrashPlan backup and restore functionality to ensure the upgrade did not break existing operations.
Caveat Minor: Review release notes for any configuration or feature changes between 5.4 and the target upgrade version

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

Fix this in Crashplan Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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