thread cc @sraub
-
-
Replying to @stanzillaz @taviso and
Yes, of course it is a valid certificate. Not seeing the issue here, care to explain?
1 reply 0 retweets 2 likes -
Replying to @sraub @stanzillaz and
The only way that could have been implemented is if the private key is embedded in the binary. That is considered a key compromise, and CA's are *obligated* to revoke it.
2 replies 0 retweets 12 likes -
Here is a relevant recent discussionhttps://groups.google.com/d/msg/mozilla.dev.security.policy/T6emeoE-lCU/-k-A2dEdAQAJ …
2 replies 1 retweet 5 likes -
and here the latest incident of this kind involving microsofthttps://www.golem.de/news/microsoft-dynamics-365-wildcard-certificate-with-a-private-key-for-everyone-1712-131544.html …
1 reply 1 retweet 1 like -
That sounds concerning but doesn't seem related. http://localbattle.net is isolated domain on purpose. connections treated as insecure and other security measures are employed as necessary.
1 reply 0 retweets 0 likes -
The attack would be a mitm replies to http://localbattle.net with a non-loopback address, extracts the private-key from the binary and then can steal authentication data or whatever.
2 replies 0 retweets 3 likes -
Replying to @taviso
I „heard“ that one of the auth methods of bnet actually just ended up with redirecting to localhost/?token= and token was valid without geo or (reasonable) time restriction, so with a bit of social eng…
2 replies 0 retweets 0 likes -
Replying to @bloerwald
"with a bit of social eng" anything is possible, that's not a vulnerability. Users reasonably expect that using hotel wi-fi will not get them compromised, they do not reasonably expect they can email strangers authentication tokens.
2 replies 0 retweets 0 likes -
Replying to @taviso
The magic url is https://eu.battle.net/login/en/flow/wow-and.app?externalChallenge=login …. If cookies and shit, it immediately redirects to http://localhost:0/?ST=$region-$hash-$id.
1 reply 0 retweets 0 likes
Well, that does seem like a bug, I don't think it's a security bug though. I'll think about it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.