Guest Users With Excessive Directory Access
Guest accounts can read more of the Microsoft Entra ID directory than they need, such as every user and group, or hold roles and group memberships beyond their purpose.
| Severity | Medium |
| CVSS 3.1 | 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Open in the calculator |
| CVSS 4.0 | 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-266: Incorrect Privilege Assignment |
| OWASP Top 10 | A06:2025 Insecure Design |
| MITRE ATT&CK | T1087.004 Cloud Account, T1069.003 Cloud Groups |
| Category | Broken Access Control |
Description
Guest users are external identities, such as suppliers and partners, invited into a Microsoft Entra ID tenant through B2B collaboration. What they can see of the directory is set by the Guest user access restrictions option in the external collaboration settings. The most inclusive choice gives guests the same access as members, letting them enumerate every user, group, group membership, device and application. The default choice limits guests' access to the properties and memberships of directory objects, and the most restrictive choice limits them to their own objects.
The finding applies where guests have member-level directory access. A guest account controlled by an attacker, whether through a compromised supplier account or a malicious individual at a partner organisation, can then map the organisation: every user name and job title for phishing and password spraying, the members of administrative and sensitive groups, and the applications and devices in use, which makes later attacks faster and better targeted.
Related weaknesses often accompany the finding: invitation settings that let any user, or even guests, invite further guests from any domain; guests holding Microsoft Entra roles or Azure role assignments; guests left in sensitive groups and Teams long after the work ended; and guests with no MFA requirement. Where guests hold roles, group memberships or Azure permissions they no longer need, the attacker gains that access too; where no such roles or memberships exist, the impact is limited to directory information.
The weakness is identified by reviewing the external collaboration settings and the roles and group memberships held by guest accounts, and confirmed by signing in as a guest and enumerating the directory through Microsoft Graph or with tools such as AzureHound and ROADtools.
Remediation
- Set Guest user access restrictions to the most restrictive choice, so that guests see only their own directory objects, or at least to the default limited choice.
- Restrict who can invite guests to users in specific administrator roles, such as Guest Inviter, or at most to members, and limit invitations to approved partner domains through the collaboration restrictions.
- Remove Microsoft Entra roles and Azure role assignments from guests unless a documented need exists, and review guests' group and Teams memberships.
- Run regular access reviews of guest accounts and remove those no longer needed.
- Require MFA for guests through Conditional Access.
Confirm the fix by signing in as a test guest and checking that other users, groups and their memberships can no longer be enumerated.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.