JustTech, LLC v. Kaseya US LLC

CourtDistrict Court, S.D. Florida
DecidedAugust 28, 2023
Docket1:22-cv-22454
StatusUnknown

This text of JustTech, LLC v. Kaseya US LLC (JustTech, LLC v. Kaseya US LLC) is published on Counsel Stack Legal Research, covering District Court, S.D. Florida primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
JustTech, LLC v. Kaseya US LLC, (S.D. Fla. 2023).

Opinion

UNITED STATES DISTRICT COURT FOR THE SOUTHERN DISTRICT OF FLORIDA MIAMI DIVISION Case Number: 22-22454-CIV-MARTINEZ JUSTTECH, LLC, Plaintiff, v. KASEYA US LLC, Defendant. / ORDER GRANTING MOTION TO DISMISS THIS CAUSE came before this Court on Defendant’s Motion to Dismiss the Complaint (the “Motion”), (ECF No. 15). This Court has reviewed the Motion, pertinent portions of the record, and applicable law and is otherwise fully advised of the premises. Accordingly, after careful consideration, the Motion is GRANTED for the reasons set forth herein. I. FACTUAL BACKGROUND Plaintiff JustTech, LLC, is a managed service provider (“MSP”) that provides IT, computer network, print, fax, and copy solution services to its downstream clients in the Mid-Atlantic and Southeast regions. (Compl. § 11, ECF No. 1.) Plaintiff creates, processes, stores, secures, and exchanges electronic data in connection with these services. (/d.) Defendant Kaseya US LLC is a global technology company that provides MSPs like Plaintiff with IT management and security software and services. (/d. § 16.) Defendant publicly promotes the safety and effectiveness of its software and services against cyberattacks by making representations online and messaging MSP customers. (/d. § 18.)

Since approximately 2016, Plaintiff has paid for Defendant’s IT management and security software and services. (Id. § 12.) Plaintiff used Defendant’s Virtual System Administrator (“VSA”) software for most of its downstream clients, opting for the on-premises product connected to a local server. (/d. J 13.) In exchange for these services, Plaintiff disclosed its clients’ electronic data to Defendant and granted Defendant certain rights to use such data. (/d.) This arrangement was governed by Defendant’s end user license agreement (the “EULA”), which users like Plaintiff must agree to without any objections or qualifications when accepting Defendant’s software and services.” Ud. § 14.) The EULA contains provisions that shield Defendant from liability related to the delivery, performance, or use of its software and services. (/d.) The EULA provides in relevant part that: Kaseya and its suppliers and licensors shall not be liable or obligated with respect to the subject matter of this agreement... or under any contract, negligence, strict liability or other legal or equitable theory . . . (II) for any cost of procurement of substitute goods, technology, services or rights, or (IID) for any incidental, indirect, special, punitive, or consequential damages (including, without limitation, loss of profits, loss of use or data, damage to systems or equipment, business interruption or cost of cover) in connection with or arising out of the delivery, performance or use of the software, documentation, any other materials provided by Kaseya or other services performed by Kaseya....

[E]xcept for Kaseya’s gross negligence or willful misconduct, Kaseya shall not be responsible or liable for the unauthorized access to, alteration of, or deletion, correction, destruction, corruption, damage, loss or failure to secure or store Customer Data.

* While this Court is generally constrained to review the four corners of the Complaint in determining whether to grant a motion to dismiss for failure to state a claim, this Court may consider documents attached to Defendant’s Motion when the document “is (1) central to the plaintiffs claim and (2) undisputed.” Day v. Taylor, 400 F.3d 1272, 1276 (11th Cir. 2005) (citing Horsley y, Feldt, 304 F.3d 1125, 1134 (11th Cir. 2002)). Because the EULA is central to the Complaint and it is undisputed that the EULA attached to Defendant’s Response to the Motion is authentic, this Court considers the EULA in addressing the Motion. See id.

[T]his Agreement is the entire agreement between Kaseya and Licensee regarding Licensee’s use of the Software, and supersedes and replaces any previous communications, representations, or agreements... (See End-User License Agreement (“EULA”) 5, 8-9, 11, ECF No. 15-1.) Plaintiff alleges that Defendant understands and has publicly acknowledged that cyberattacks on MSPs present heightened risks and consequences because the attack affects the MSP and its downstream clients. (/d. §§ 20, 24.) Defendant has frequently reported on cyber- and ransomware attacks and provided guidance on how to minimize their associated risks. (/d. □ 26.) One risk-prevention method Defendant promotes is to timely discover and “patch” or fix software vulnerabilities. (/d. § 33.) Industry guidelines recommend that third-party users be warned of such software vulnerability risks in a timely manner. (/d. { 31.) On April 6, 2021, the Dutch Institute for Vulnerability Disclosure (the “DIVD”), an international team of voluntary computer researchers that investigates and reports software vulnerabilities, warned Defendant that its VSA software contained multiple, critical vulnerabilities. (/d. § 36.) These vulnerabilities were critical due to their “zero-day” nature (meaning that hackers could exploit them immediately) and potential to affect Plaintiff's clients in the defense, aerospace, medical, transport, financial, and energy markets. (/d. §37.) Defendant and the DIVD worked together to address the VSA vulnerabilities, but Plaintiff alleges that progress stalled on patching the vulnerabilities. (/d. § 40.) Scheduled patches of the vulnerabilities were spread out and included dates after the date of the ransomware attack that prompted this dispute. (/d.) Plaintiff alleges that it was unaware of these vulnerabilities in the VSA software, and that Defendant failed to issue any warnings or implement additional cybersecurity measures. (/d. § 41.)

Defendant was also warned of cybersecurity concerns from its own employees in the years leading up to the ransomware attack. (/d. 444.) Between 2017 and 2020, Defendant’s engineers and developers warned the company of these concerns, and other employees reported that company executives were made aware of the numerous problems with the VSA software. Ud. J] 44-45.) Former employees considered Defendant’s decision to outsource work to Belarus, a country with close ties to Russia, as another potential security issue because, Plaintiff alleges, many cybercriminals operate in Russia. (/d. § 46.) A Russian-based criminal operation known as REvil was determined to be the source of the July 2, 2021, ransomware attack on Defendant’s VSA software that disrupted operations for Plaintiff and its downstream clients. (/d. 9 47.) REvil completed this attack by exploiting the VSA software vulnerabilities. (/d.) Around 12:30 p.m. on July 2, 2021, over one thousand devices managed by Plaintiff became inaccessible and displayed a document explaining that all of Plaintiff s files had been encrypted by a third party and would not be made accessible until Plaintiff followed further instructions. (/d. §§ 48-49.) Plaintiff was informed it would lose this data if it failed to pay $45,000.00 ransom for each encrypted device. (/d. §49.) All of Plaintiff's downstream clients connected to the VSA software were affected. Ud. § 50.) Within eight minutes of the attack, Plaintiff shut down the VSA system and instructed its downstream clients to shut down all computers in their systems until further notice. Ud. 51.) At 4:00 p.m., Defendant publicly disclosed that a “limited,” “potential” attack on its VSA servers took place that afternoon and recommended users to shut down all VSA servers. (/d. § 52.) Defendant claimed to have followed an “established incident response process to determine the scope of the incident and the extent that our customers were affected.” (/d. § 53.) Defendant believed it had identified the source of the vulnerability and began preparing a patch to mitigate

its risks.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Neal Horsley v. Gloria Feldt
304 F.3d 1125 (Eleventh Circuit, 2002)
Robert Garfield v. NDCHealth Corporation
466 F.3d 1255 (Eleventh Circuit, 2006)
Financial SEC. Assur., Inc. v. Stephens, Inc.
500 F.3d 1276 (Eleventh Circuit, 2007)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
American Dental Assoc. v. Cigna Corp.
605 F.3d 1283 (Eleventh Circuit, 2010)
Michael McGee v. JP Morgan Chase Bank, NA
520 F. App'x 829 (Eleventh Circuit, 2013)
Rollins, Inc. v. Heller
454 So. 2d 580 (District Court of Appeal of Florida, 1984)
Samuels v. King Motor Co. of Fort Lauderdale
782 So. 2d 489 (District Court of Appeal of Florida, 2001)
Bates v. Rosique
777 So. 2d 980 (District Court of Appeal of Florida, 2001)
Paszamant v. Retirement Accounts, Inc.
776 So. 2d 1049 (District Court of Appeal of Florida, 2001)
Taylor v. Maness
941 So. 2d 559 (District Court of Appeal of Florida, 2006)
TRG Night Hawk Ltd. v. Registry Development Corp.
17 So. 3d 782 (District Court of Appeal of Florida, 2009)
Townsend Contracting v. JENSEN CIV. CONST.
728 So. 2d 297 (District Court of Appeal of Florida, 1999)
Garcia v. Santa Maria Resort, Inc.
528 F. Supp. 2d 1283 (S.D. Florida, 2007)
Simon v. Celebration Co.
883 So. 2d 826 (District Court of Appeal of Florida, 2004)
Century 21 Admiral's Port, Inc. v. Walker
471 So. 2d 544 (District Court of Appeal of Florida, 1985)
Urling v. Helms Exterminators, Inc.
468 So. 2d 451 (District Court of Appeal of Florida, 1985)
Bankers Trust Co. v. Basciano
960 So. 2d 773 (District Court of Appeal of Florida, 2007)
HTP, Ltd. v. Lineas Aereas Costarricenses
685 So. 2d 1238 (Supreme Court of Florida, 1996)

Cite This Page — Counsel Stack

Bluebook (online)
JustTech, LLC v. Kaseya US LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/justtech-llc-v-kaseya-us-llc-flsd-2023.