artemis tack

Entra

October 01, 2026

Sharepoint. It’s a word that strikes a heart of fear in many sysadmins, at least that’s what I imagine after having done some exploring with it. And that’s for good reason, Microsoft Sharepoint fucking sucks from a security standpoint. I think part of that is because Microsoft’s naming and marketing is fucking bad. Like, what the hell is Sharepoint in the first place? Even I’m not 100% sure and I’ve spent time basically doing offensive security using OSINT principles on my universities Sharepoint. From what I’ve gathered it’s kinda like Onedrive. But then it also has a shared Onenote notebook and site for some reason? I’m really not quite sure, but what I am sure is that when you give users the ability to upload documents to something some users are bound to share them with the wrong permissions, and that’s what happened here. The Sharepoint side of the story is really the story of improperly configured sharing permissions, along with a health dose of “why the fuck would you upload that to your work account????????”

On the Entra side of things is where it gets more interesting. I’m not sure (==look up to verify if this is true or not before publishing==), but I’m pretty sure that a group is created whenever a whole host of actions take place. Or at least it’s the only explanation that makes sense to me as to why there would be over 75,000 groups domain wide. And I really want to highlight two key facts around the groups that’re created; the most interesting ones have a shared inbox, and they were set to public instead of private. I can’t stress enough how much this is on user misconfiguration, because by default when you create a group for something it sets the group to private. You have to manually set it to be public. And, as is going to become increasingly apparent, I can’t figure out why you would do that. An easy solution to this problem at the sysadmin level is to just disallow groups to be anything other than private. For some groups, especially those focused on a shared Teams chat that’s meant to be accessible for anyone in the org it can create a bottleneck. But I’d imagine that for most orgs it’s worth the tradeoff to have slightly more annoyed end users having to manually accept invites to groups rather than have the potential for misconfiguration. And I suppose that’s another thing, you can request access to groups. So if the person who’s on the other end isn’t 100% sure what they’re doing they could unknowingly just accept a random person and they’d just be there in the group; Pete Hegseth Signalgate style. I am tempted to try this, but I haven’t quite yet.

Side note: As I would later find out the campus Linux admins group, which I was initially stoked to be added to, ironically turned out to be one of the only groups that I found that had a legitimate reason to be public. For a different project mapping my universities internal http/https DNS records (I’ll probably write a blog post on that sometime in the future depending on what I find) I found a site that had a blurb about the group. Apparently it’s supposed to be a Teams group chat (and, can confirm, it did in fact have a Teams chat) for Linux users on campus, especially Linux users and admins on campus. And the site, very much publicly facing, had a direct link to join the Teams chat. Other than cases like that, I can’t imagine what reason someone would have to make a publicly available group, especially a shared inbox!

But I’m getting ahead of myself. I’ve always found that the best security blog posts have a good story, so I’ll start there. It was a nippy October day, and I had just gone to my universities Hacking club meeting, and then out for a bite to eat afterwords. After that I got to talking about one of them about some things that I had found in Sharepoint a month prior. They brought up Microsft Entra, and I happened to look at the “groups” page of my profile. There I could see all the groups that I was a member of, as well as a button to add myself to groups. And so I searched “admin” and tried adding myself to the first group that popped up. That failed. I then tried adding myself to a couple other random groups, thinking that I couldn’t add myself to any groups. But one of them worked! This meant that I could add myself to any group that I wanted! And so I then searched “admin” and tried adding myself to the first 250 results (that’s the max number that the search will populate). And, to my surprise, some of the groups I was able to add myself to!

And so, for the next couple of hours, I just randomly searched for interesting keywords like “admin”, “sysadmin”, “linux”, “office”. Things like that. Before I knew it I had several hundred random groups that I had added myself to. Most weren’t interesting, just random test groups, but there were a couple that stuck out. Like the aforementioned Linux Campus Admins group. At the time I wasn’t quite sure what I was doing. I knew that I was adding myself to something, but I wasn’t sure what would change. Would I magically have sudo access on all the machines on campus that I sshed into? Would I be able to log into things that were restricted? I didn’t know, so all did was hope that it was something interesting. Around 04:00 I finally decided to call it a night, took my meds, and hit the hay.

When I woke up I looked at my phone, which was flooded with Outlook notifications about being added to different groups. I cleared those notifications and opened up Outlook on my phone to delete all those notification emails so that my already disaster of an inbox didn’t get any worse. And, amongst those emails, were some emails that were sent to some of the groups that I had added myself to. One feature of groups is a shared inbox, and I could now view all the emails in that inbox! And here was some of the most interesting things that I found.

As it turns out, when people think that nobody’s looking they’ll send all sorts of things that they probably shouldn’t. I was able to find records of sexual abuse on campus. I was able to find maintenance records of the power plant on campus. I was able to find the grades of some students. And I’m sure that, or at least I hope that, there are more official (re: secure) ways of communicating these records, but here they were for the world to see. Or at least anybody who happened to add themselves to whatever group the messages corresponded to.

Manually adding myself to groups was fun, but I wondered if there was a faster way, surely, right! Well yes, my dear madam, there is indeed a faster way! For how much I tend to shit talk Microsoft, I have to admit, Powershell is actually pretty good, and I actually enjoy working with it. Hot take, but maybe even more than BASH. But there’s an ad Powershell module, and using it I can get a list of every group in the organization, and then attempt to add myself to every group. So I set up that little script, and just set it running. All in all it took about two days to complete, and I was able to add myself to about 2,500 groups.

There are two important things to note about this approach. The first is that it creates a lot of noise, and the second is that, as long as logging is set up properly, it’s traceable back to you. Microsoft Entra creates a log each time that I tried to add myself to a group, meaning that I just created 75,000 entries in the log, about 73,000 of those were failures due to incorrect permissions. One would think that you could set up some sort of automatic detection system to try and detect this. Because there’s pretty much no legitimate reason for someone to try and do that, so if someone is trying to do that it’s probably worth looking into. I was also going at a rate of about 1/sec for a steady 48 hours, and you’d think that it would raise some flags and start to rate limit my account, but nope! I was free to just do as I pleased, which is odd. Again, there’s pretty much no legitimate reason for a account to try and add themselves to 75,000 groups, and I especially would have thought that the numerous failures would have raised some flags, but apparently not.

When I saw this I was like, “shit, shit, shit. This isn’t good.” And it’s one of those things where the potential for something happening, like someone exploiting this, was very low. But the potential impact of someone doing something with this data is so high that my heart kinda started to sink. Like this is extremely sensitive information, that, if it were to leak, in the case of abuse details, could be life or death type of shit. And so, upon seeing this, I decided to go straight to the top; the CISO. We met, and had a good meeting where we talked about what we were going to do about the issue. And, a few weeks later, the problem was fixed.