![\"Dell](\"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2015\/11\/dell_logo.png\" "\\"dell_logo.png\\""){kind=logo}
<\/p>\n<\/p>\n
eDellRoot<\/code>.<\/li>\n- Initially it was thought it only affected laptops sold since August, then it emerged that it was on Desktops too, and the last shoe to drop was that the cert was also being pushed to people with older Dell computers via updates to the Dell software.<\/li>\n
- This root cert is installed with its ‘PRIVATE’ key<\/strong>, and all computers have certs with the same private key<\/strong>, and the password ‘protecting’ that private key is
dell<\/code>.<\/li>\n- A second, similar cert was found later in the week also from Dell called
DSDTestProvider<\/code>.<\/li>\n<\/p>\n
- The second cert is not pre-installed on Dells, but comes along for the ride when ever a user installs the Dell System Detect<\/em> support tool, which Dell support often ask users to do. Dell say: “The impact from Dell System Detect is limited to customers who used the ‘detect product’ functionality on our support site between October 20 and November 24, 2015”<\/em><\/li>\n
- Reports also emerged that Dell Foundation Services<\/em> can be tricked into revealing a Dell’s unique service tag<\/em> to any website.<\/li>\n<\/ul>\n
What The Bad Root Certs Mean:<\/h4>\n\n- It is trivial for attackers to get a copy of the private key (it can be extracted from any affected Dell, and it is now all over the internet) and issue fraudulent TLS certs for any website on the planet. All Dell computers with the
eDellRoot<\/code> cert installed will see these fraudulent certs as valid – effectively removing all the protection HTTPS should provide, and rendering every secure website on the planet insecure.<\/li>\n- Dell did not even apply limitations to this cert, so, it can be used for everything<\/strong> a cert can be used for, not just HTTPS – e.g. it can be used for creating fake S\/MIME email certs, fake VPN certs, and even fake code signing certs. Basically, everything that relies on the PKI (public key infrastructure) is insecure on an infested Dell.<\/li>\n
- Bottom Line – if your computer has the
eDellRoot<\/code> cert installed, every single website on the planet is insecure, every single VPN is insecure, every single signed and\/or encrypted email is insecure, basically, everything that relies on the PKI (Public Key Infrastructure) is insecure for you.<\/li>\n<\/ul>\nComparisons to Lenovo’s SuperFish Debacle:<\/h4>\n\n- Lenovo’s motivations were different – they installed an utterly insecure root certificate to advertise at you, while Dell say they did it to make customer support easier.<\/li>\n
- However, why they did what they did is irrelevant – both made the same blunder, and both torpedoed their users security in the same way. The only small difference is that Dell’s cert is even more powerful than SuperFish’s one, so Dell managed to make the same mistake just that little bit worse.<\/li>\n<\/ul>\n
What the Service Tag Disclosure Bug Means:<\/h4>\n\n- The service tag is unique to each computer, so having it available to websites makes it the absolute ultimate cookie – a unique ID for your computer that you cannot change that follows you everywhere you go on the net.<\/li>\n
- Privacy is impossible if websites can access your service tag.<\/li>\n<\/ul>\n
You have a Dell – now what?<\/h4>\n\n- There are many free testers to check if you have the dodgy certs (the tests have to be done from IE or Chrome, not from FireFox) – e.g. edell.tlsfun.de<\/a><\/li>\n
- Dell have released removal instructions (as a DocX file instead of a web page) – dellupdater.dell.com\/Downloads\/APP009\/eDellRootCertRemovalInstructions.docx<\/a><\/li>\n
- Dell have also released a removal tool (I don’t know if it does both certs – better to do the removal manually IMO) – dellupdater.dell.com\/Downloads\/APP009\/eDellRootCertFix.exe<\/a><\/li>\n
- My advice is to un-install all the Dell crapware on your computer – personally, I do a full nuke-and-pave of all PCs because all manufacturers put crap on Windows PCs, and I don’t trust any of them. Once the Dell rubbish is removed, then remove the certs. (if you remove the certs first they may be put back by the apps before they get killed.)<\/li>\n<\/ul>\n
Links:<\/h4>\n\n- Dell’s Official Response: en.community.dell.com\/dell-blogs<\/a><\/li>\n
- Ars Technica’s report in the service tag disclosure problem: arstechnica.com\/security\/2015\/11\/pcs-running-dell-support-app-can-be-uniquely-idd-by-snoops-and-scammers<\/a><\/li>\n
- Naked Security’s write-up of this mess: nakedsecurity.sophos.com\/2015\/11\/25\/dell-installs-risky-superfish-style-security-certificates-heres-what-to-do<\/a><\/li>\n
- Brian Krebs’ write-up of this mess: krebsonsecurity.com\/2015\/11\/security-bug-in-dell-pcs-shipped-since-815<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
What Happened: This week it emerged that Dell started rolling out an updated version of it’s Dell Foundation Services software (or crapware as I call it) that comes with a root certificate that gets installed into Windows. The certificate shows up in the Windows Certificate Manager as eDellRoot. Initially it was thought it only affected […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[147,1],"tags":[],"class_list":["post-7523","post","type-post","status-publish","format-standard","hentry","category-blog-posts","category-podcasts"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/7523","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=7523"}],"version-history":[{"count":7,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/7523\/revisions"}],"predecessor-version":[{"id":7539,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/7523\/revisions\/7539"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=7523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=7523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=7523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}