And when the vulnerability is caused by something as fundamental as certificate validation, it should obviously be fixed. We all understand MITM risks are a serious problem, no matter how slim the chances of exploit under different scenarios may be. There’s a bit of a story in the podcast about the difficulties that the individual who found the bug encountered while trying to get Microsoft Security to acknowledge that it was a legitimate issue. An attacker could hijack an authentication token from the session, which would be valid for up to 10 minutes, and perform administration tasks with all the privileges of the authenticated user.
The security issue is basically a lack of proper certificate validation that leaves EXOPS vulnerable to man-in-the-middle (MITM) attacks. I have listened to the podcast twice (once the first time, and then a second time to make some notes for this article) and it seems they’re referring to the Exchange Online Remote PowerShell module, aka EXOPS.
A recent episode of the popular Risky Business infosec podcast titled “Good Microsoft, Bad Microsoft” discusses a security vulnerability in a PowerShell tool used to manage Exchange Online.
0 kommentar(er)
