3 ms·
I wonder what the lapse in design was. It'd be nice of Huawei disclosed what type of security vulnerability it was and how they fixed it.
by djsumdog 8y ago
I wonder what the lapse in design was. It'd be nice of Huawei disclosed what type of security vulnerability it was and how they fixed it.
- monocasa 8y agoMicrosoft has a good write up on the flaw at least. https://www.microsoft.com/security/blog/2019/03/25/from-alert-to-driver-vulnerability-microsoft-defender-atp-investigation-unearths-privilege-escalation-flaw/ https://www.microsoft.com/security/blog/2019/03/25/from-aler...
- criddell 8y agoMaybe they named the key _NSAKEY which created a namespace collision with a totally non-NSA key that Microsoft added years ago. Just in case you hadn't already seen this: https://en.wikipedia.org/wiki/NSAKEY https://en.wikipedia.org/wiki/NSAKEY
- zigzaggy 8y agoThanks for this new information. It’s especially hilarious that Mr. Campbell was accused of being a conspiracy theorist for thinking _NSAKEY would be exactly what it sounds like. Even better, it turns out the key WAS for the NSA (!) “because the NSA is the technical review authority for U.S. export controls.” How convenient. Sorry I’m not buying it. I worked in .gov contracting long enough to smell a cover story.
- ryanlol 8y agoWell then, get your disassembler out and find the evidence of this backdoor nobody else has managed to find in the past two decades. The whole NSAKEY story is a laughable fabrication, nobody has ever described the mechanism by which the backdoor is supposed to work. This should be a trivial exercise.