XCPE Backdoor: Why Firmware Certification Isn't Enough

DEV Community

Certified Device Firmware Is Admission Evidence. It Is Not Behavior Assurance.A

Certified device firmware is evidence that a device was admitted, not evidence of how it will behave once it is running. On November 2, Google's Threat Intelligence Group reported that the XCPE backdoor, which it found built directly into many device models and brands, had enrolled more than 1.3 million set-top boxes into a botnet. Google assesses with high confidence that Videostrong Technology, an Android OEM and ODM, intentionally developed, deployed and operated the backdoor and botnet for financial gain, and says Videostrong used obfuscation to exploit a gap in Google's own tests and load malicious code after first boot. The incident is easy to file as one more bad supplier. The narrower question is what a buyer still holds when the manufacturer was known to the certifier and was itself the source of the risk. What Google Established About XCPE, and What It Did Not For modern infrastructure architecture, the usable question is narrow, so the evidence boundary comes first. The middle column is Google's report, attributed to Google. The right column is what the report does not say. Topic Google reports Not stated Attribution A high-confidence assessment that Videostrong intentionally developed, deployed and operated the backdoor and botnet for financial gain. Google also says it believes the campaign was not an isolated rogue insider or a development oversight. An adjudicated finding. Videostrong's own account does not appear in the report. Persistence A stub preloaded in the firmware partition and running at system privilege. If a user uninstalls the backdoor, it reinstalls from the /oem/ partition on reboot. How the stub or the /oem/ package entered the firmware build. First boot Obfuscation exploited a gap in Google's tests, and malicious code loaded after the device's first boot. Which image Google tested, which tests, the nature of the gap, or any dormant period. Google's action Videostrong was banned from making devices with preloaded Google apps, and from building and selling certified Android devices or supplying software to other certified vendors. Google also took legal action against control domains and servers, changed its review process, and is improving firmware integrity assurance on certified Android TV devices. Revocation of certification on shipped devices, blocking them, notifying owners, or what the review changes are. Population More than 1.3 million set-top boxes, plus other Android-based devices Google observed: telehealth, karaoke machines and digital signage. Counts, brands or models for the non-set-top devices, enterprise deployment, or which affected devices were certified. Keep the populations apart. The 1.3 million figure counts set-top boxes enrolled in the XCPE botnet. The at-least-10-million figure is Google's assessment of additional devices behind the affiliates' own command domains, which also distributed through other channels. They are different populations and should not be added. Plume Security Labs, a partner in the takedown, published its own whitepaper. It states that the fleet mixes AOSP and Google-certified devices, in one sentence, with no method for determining certification status and no counts. Google's report does not say which affected devices were certified. This note treats that question as open and writes about the class of certified OEM firmware. Scope: OEM-controlled firmware behavior on Android devices a buyer deploys, such as signage, telehealth and set-top. Google does not say these were enterprise deployments; that is this note's buyer scenario. No claim is made about server firmware, BMC or UEFI. Certified Device Firmware Is an Admission Test Google describes certification as a comprehensive suite of compatibility and security tests that OEMs must go through. That establishes an admission process, but the report does not identify which firmware image was examined, which tests were applied to it, or how the tested image relates to the firmware that shipped. Cert...

Powered by Readybot.io