Wiz Researchers Show How Azure AD Misconfiguration Enabled Bing Content Changes and XSS

· Original article ↗

Summary

Wiz researchers found that poorly validated multi-tenant Azure AD apps exposed Microsoft applications, including Bing Trivia. They demonstrated search-result manipulation and an XSS attack that accessed Office 365 data from their test account.

Key points

  • The researchers said about 25% of the multi-tenant applications they scanned were vulnerable to authentication bypass because applications did not properly validate users’ identities and access.
  • Using an account from another Azure tenant, they accessed Bing Trivia and changed content that appeared in Bing search results.
  • They demonstrated XSS and used it to obtain an Office 365 token from their test account, then access that account’s emails and other data.
  • Wiz also reported similar exposure in other Microsoft applications, including tools for newsletters, notifications, customer support, and file management.
  • The researchers reported the issues to Microsoft; Microsoft said the affected applications were fixed by March 20, 2023, and updated Azure AD guidance and functionality.
  • For remediation, the article recommends disabling multi-tenancy when unnecessary or enforcing access through user assignment, conditional access, or claims-based authorization checks.

Article Details

Attack Vectors
  • Misconfigured multi-tenant Azure Active Directory applications accepted sign-ins from users in other tenants without sufficient authorization or token-claim validation.
  • Researchers used an account from their own Azure tenant to access the Bing Trivia CMS, then changed content that appeared in Bing search results.
  • The researchers tested an XSS payload through the CMS; they reported that it could retrieve an Office 365 token and access data associated with the user. The article says a malicious actor could have used this method against Bing users.
  • Other exposed Microsoft applications included panels or APIs that could send arbitrary emails, read or send internal notifications, control call-center agents, edit blog posts, and access internal files.
Defensive Notes
  • Use single-tenant authentication when external tenancy is not required.
  • For required external access, consider user assignment or conditional access policies, and implement claims-based authorization and token checks in application code.
  • Review Azure AD service principals and application registrations for multi-tenant access; test whether a user from a different tenant can sign in when that access is not intended.
  • Because Azure Active Directory logs may not show past activity sufficiently, review application logs for suspicious sign-ins.
  • The article reports that Microsoft fixed the applications reported by Wiz Research and updated customer guidance.

MITRE ATT&CK

People

Vendors

Products

Tools

Related Articles