Bodysnatcher "OpenId Provider" attack question -
okay here's bodysnatcher openid provider attack scenario.
bob's google claimed identifier following, ttps://www.google.com/accounts/o8/id?id=aatawkqvytybnnuhprhn36f8mlvfijvzg8tene
jane has how found bob's "current" claimed identifier.
she goes off , creates here own openid provider, www.jane.com/accounts/o8/id, such when asked return bob's claimed identifier.
she goes badly coded site, www.bcs.com, uses open id , bob has account at.
she tells www.bcs.com use openid provider www.jane.com/accounts/o8/id.
now part don't know , know if it's possible/realistic... www.jane.com/id how gets www.bcs.com believe claimed identifier "string" (i.e. value site see) ttps://www.google.com/accounts/o8/id?id=aatawkqvytybnnuhprhn36f8mlvfijvzg8tene.
is possible, how, though host www.jane.com?
we're working implement openid , don't want "badly coded site". we're using thirdparty .net library gives claimed identifier we're not sure or how builds it. if possible faked we're considering doing checks provider openid's url matches in claimed identifier.
this brings concern whether should take step of hashing/scrambling our claimed identifiers. think so, because google changes identifier based on site requesting openid. mean why else go trouble of doing if not try , protect members?
you're asking if possible write implementation of openid consumer violates specification enough introduce security vulnerabilities. yes, is. omit whole validation process , believe you're told user.
but consumer closely follows openid specification, such attack not possible.
since said use .net library, use dotnetopenauth. it's same library stackoverflow uses, , don't have worry vulnerabilities when using it. if you're using library, it's best choice switch dotnetopenauth.
as reason google return realm-based identifiers: done protect it's users' privacy, not increase security. basically, ensures can't link user's account google account.
Comments
Post a Comment