• BaldProphet
    link
    fedilink
    611 months ago

    My question is who thought it was a good idea to put a test account on a production system?

    • @[email protected]
      link
      fedilink
      English
      711 months ago

      Sometimes you need to verify a production bug, and you need an account with which to do so

    • @LemmyIsFantastic
      link
      211 months ago

      Does it really matter? MS is huge. Shit like this is going to happen from time to time. They detected it, reported it, and moved on.

  • AutoTL;DRB
    link
    fedilink
    English
    111 months ago

    This is the best summary I could come up with:


    The hackers who recently broke into Microsoft’s network and monitored top executives’ email for two months did so by gaining access to an aging test account with administrative privileges, a major gaffe on the company’s part, a researcher said.

    In Thursday’s post updating customers on findings from its ongoing investigation, Microsoft provided more details on how the hackers achieved this monumental escalation of access.

    In Thursday’s update, Microsoft officials said as much, although in language that largely obscured the extent of the major blunder.

    Threat actors like Midnight Blizzard compromise user accounts to create, modify, and grant high permissions to OAuth applications that they can misuse to hide malicious activity.

    They created a new user account to grant consent in the Microsoft corporate environment to the actor controlled malicious OAuth applications.

    The threat actor then used the legacy test OAuth application to grant them the Office 365 Exchange Online full_access_as_app role, which allows access to mailboxes.


    The original article contains 339 words, the summary contains 156 words. Saved 54%. I’m a bot and I’m open source!