You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The BMC can be pwned from the OS (e.g. firmware updates, IPMI exploits, probably many other ways). Assume the BMC can be pwned from the network (original tweet). The BMC can pwn the OS (direct memory access). If all your BMCs are networked together, you can jump between hosts.
Conclusion: the only safe way is to isolate every BMC from every other BMC, and from everything else, behind a 2FA-secured frontend.
Ok cool, I didn't miss anything. Twitter is far far too terse to convey all the nuance. Thx.
TL;DR: isolating BMCs on a dedicated LAN isn't enough: attackers can compromise a host, then its BMC, then other BMCs on the LAN, then other hosts. You absolutely want them on a private VLAN or on separate L2 segments with a firewall.
And a bmc should be isolated. If a bmc can see other bmc, they can spread the fun
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
