HN

Comments (23)

• unddoch
  If anyone from Microsoft security reads this, could you please do something about login.microsoftonline.com/XXX/v2.0/adminconsent?The callback you're redirecting the user to at the end of that flow is forgeable if an attacker knows an azure tenant ID of a different customer, and putting a "Never use the tenant ID value of the tenant parameter to authenticate or authorize users" warning in the docs is only helpful as long as a way to authenticate users exists.
• Menu

  meekins
  When it comes to the amount of cross-tenant leaks Azure looks to be way ahead the competition. Makes me wonder why enterprises still flock there.
• Menu

  albert_e
  maybe we should tag submissions with dates now?[2026-10-02]beginning of curent month feels like two years ago when multiple vulns drop daily
• outworlder
  Ok so.Microsoft had an egregious cross-tenant vulnerability (really, how many cross-tenant vulnerabilities did other clouds have?).Vulnerability was reported.They fixed it - incorrectly. Reported again.They fixed it this time... and broke the previous fix. So it's vulnerable again.What a clown show.
• Menu

  thewisenerd
  path traversal and IDOR..likely been active since the inception of these capabilitieswonder if the recommendation to "add randomness to resource names" is because of this (unrelated security by obscurity lol)
• xmcp123
  God. I would hate to be the engineer forced to have enough Azure experience to be able to find these bugs and understand Azure’s infrastructure on this level.Should have been addressed in the Geneva conventions.
• Menu

  eugenekay
  Reporting cross-Tenant issues as an outsider with a vulnerability chain gets you $$$.Reporting “theoretical” issues with validation as an Employee gets you a lot of questions as to why you were looking.Oh well.
• klorbrinnbor
  [flagged]