Attack Chain

1. Physical Access: An attacker gains physical access to a vulnerable Shark RV2320EDUS robot vacuum.
2. Credential Access (Device Root Shell): The attacker disassembles the vacuum, connects to UART pins on the mainboard, bypasses the U-Boot console password, and exploits a boot argument (init=/bin/sh) to obtain a root shell on the device.
3. Credential Access (Certificate Extraction): From the root shell, the attacker extracts the per-device AWS IoT key and certificate files located at /mnt/res/vapp/certs/.
4. Abuse of Cloud Identity: Using the extracted certificate, which possesses an overly permissive AWS IoT policy (allowing publish/subscribe on $aws/things/#), the attacker connects to SharkNinja's cloud broker.
5. Discovery & Targeting: The attacker subscribes to $aws/things/# via the broker to observe traffic and harvest serial numbers of other Shark vacuums operating in the same AWS region.
6. Remote Code Execution: The attacker publishes a shadow update containing an Exec_Command field to the specific topic of a targeted Shark vacuum.
7. Impact (Remote Control & Data Exfiltration): The targeted vacuum's appd management daemon reads the Exec_Command field, which is executed via popen, providing the attacker with capabilities such as establishing a reverse shell, accessing live camera feeds, reading house maps, and exfiltrating plaintext Wi-Fi passwords.

Impact

The successful exploitation of this vulnerability would allow an attacker to remotely control affected Shark robot vacuums, leading to significant privacy and security compromises. Attackers could view sensitive household information through the vacuum's camera, map out the interior of homes, and steal Wi-Fi network credentials, potentially enabling further network intrusion. While the researcher tested on his own devices, the identified scope suggests that hundreds of thousands of Shark vacuums across a single AWS region could be vulnerable. SharkNinja has not yet patched the flaw or issued an official advisory, leaving devices exposed to these risks. The only current owner-side mitigation is to disconnect the vacuum from Wi-Fi, which disables app control and smart features.

Recommendation

• Monitor Vendor Advisories: Regularly check SharkNinja's official channels for an upcoming security advisory or patch regarding this vulnerability.
• Review IoT Device Policies: For organizations that manage IoT fleets, review AWS IoT Device Defender audit checks, specifically IOT_POLICY_OVERLY_PERMISSIVE_CHECK, to ensure device policies are properly scoped to iot:Connection.Thing.ThingName and not aws/things/*. This is a vendor-side fix, but awareness is crucial.
• Isolate or Disconnect Affected Devices: Until a vendor-supplied patch is available, end-users should consider disconnecting affected Shark vacuums, such as the Shark RV2320EDUS and AV1102ARUS, from their Wi-Fi networks to prevent remote exploitation.