‹ BackHN Continuity

Thread

I could've accessed 17T Microsoft records

322 points · 128 comments · luispa

  1. er0k · · focus · HN ↗
    wow I am so surprised to hear once again how JWTs are terrible

    <a href="https:&#x2F;&#x2F;www.howmanydayssinceajwtalgnonevuln.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.howmanydayssinceajwtalgnonevuln.com&#x2F;

    1. fabian2k · · focus · HN ↗
      Someone not verifying the signature at all is not a mistake where you can blame the JWT spec itself.
      1. meindnoch · · focus · HN ↗
        They did verify the signature, and it was correct according to the &quot;none&quot; algorithm.
        1. teamolHuang · · focus · HN ↗
          They edited the payload first but signature was never changed. A JWT&#x27;s signature changes if payload changes; so it was never about the &quot;none&quot; algo, it was that Microsoft never validated the JWT with their signing key.

          JWT is a great tool, Microsoft just failed to use it correctly.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.