|
@MGrafnetter | |||||
|
If you deployed Windows Hello for Business, you should definitely read Microsoft's Security Advisory ADV190026.
portal.msrc.microsoft.com/en-US/security…
And I am not saying it just because I reported that issue and had a talk about it at Black Hat Europe. 😉
blackhat.com/eu-19/briefing… #BHEU pic.twitter.com/BUKgzAc33b
|
||||||
|
||||||
|
Jaromir Kaspar
@jaromirkaspar
|
9. pro |
|
how do I find that my TPM is vulnerable? is there some xml/json with list of versions and models? if I understand correctly, correct way is to flash new firmware, wipe and initialize TPM and reissue WHfB identity?
|
||
|
|
||
|
📔 Michael Grafnetter
@MGrafnetter
|
9. pro |
|
Additionally, you have to manually delete those vulnerable public keys from AD, which is not obvious at all. There is a script for local checking of vulnerable TPMs, or you can check event logs, see portal.msrc.microsoft.com/en-us/security…
There is also an undocumented ADFS key auditing option.
|
||
|
|
||