The Spanner logo
    • Home
    • Blog
      • Blog home
      • RSS
    • Login
    • Home
    • Blog
      • Blog home
      • RSS
    • Login
    The Spanner logo

    The Spanner
    Web security blog

    Made by Gareth Heyes
    Follow me on Twitter: @garethheyes

    Javascript for hackers!

    Hackvertor logo
    Shazzer logo
    My Github account
    Recent posts
    Introducing Feedworm: A Privacy-First RSS Reader That Lives in DevToolsSpeedy RSVP extensionAutoVaderHackvertor history and tag finderShadow Repeater v1.2.3 releaseBurp Hackvertor v2.1.24 releaseHacking roomsXSSing TypeErrors in SafarivalueOf: Another way to get thisMaking the Unexploitable Exploitable with X-Mixed-Replace on FirefoxThe curious case of the evt parameterCSS-Only Tic Tac Toe ChallengeRewriting relative urls with the base tag in SafariBypassing DOMPurify with mXSSNew IE mutation vectorHow I smashed MentalJSMentalJS DOM bypassAnother XSS auditor bypassXSS Auditor bypassBypassing the IE XSS filterUnbreakable filterMentalJS bypassesmXSSJava SerializationBypassing the XSS filter using function reassignmentRPOSandboxed jQueryX-Domain scroll detection on IE using focusEpic fail IEnew operatorDecoding complex non-alphanumeric JavaScriptHacking FirefoxDOM ClobberingBypassing XSS AuditorThe evolution of codeNon-Alpha PHP in 6-7 charsetTweetable PHP-Non AlphaMentalJS for PHPOpera x domain with video tutorialSandboxing and parsing jQuery in 100ms

    What is OpenID and why hasn't it been setup correctly?

    By Gareth Heyes (@hackvertor)

    Published 19 years 2 months ago • Last updated March 22, 2025 • ⏱️ 2 min read

    ← Back to articles

    How it works

    You place a tag on your blog/website which links to the OpenID server provider. Using this tag the OpenID server confirms that your blog should use authorisation through it's service. So when you enter your blog into a OpenID enabled web site it will ask for your password on the OpenID provider's service.

    What do you mean it hasn't been setup correctly?

    Well the hole in this service is the fact that in the specification it allows you login to a web site without a password, how so you say? Well when you login to the OpenID provider you enter your password and it remembers it (caches it) allowing any web site in the world to possibly abuse this.

    Huh? I want proof

    Well I'm currently working on some more concept code to prove my theory but I've already produced an example that affected many OpenID providers.

    http://janrain.com/blog/2007/03/22/myopenid-security-fix/

    Why do you care?

    I can see the OpenID service being very popular and therefore producing a huge security risk, I care because I don't want a huge chunk of the internet exploited by the bad guys.

    What's your solution?

    Easy! Ask for the password everytime a request to login to a web site is made. The OpenID provider needs to do this in order to prevent the attack above and also many other possible attacks. I want the OpenID specification to be changed to force OpenID providers to always ask for your password.

    ← Back to articles