Re:Kristall – a browser without support for CSS/JS/WASM or g...
by moring on Thursday January 12, 2023 @02:15PM
(#34358885)
My guess would be: using CSS to place the malicious site's input files exactly where the framed site's input fields are, but "on top" (on the z axis), so the user actually inputs data into the malicious site.
Re:Kristall – a browser without support for CSS/JS/WASM or g...
by meindnoch on Thursday January 12, 2023 @03:49PM
(#34360050)
How is this “attack” any different than simply mirroring the site? The URL bar shows the malicious site either way. If you enter your password on the malicious site, you’re pwned. Don’t need frames for that.
Re:Kristall – a browser without support for CSS/JS/WASM or g...
by shadowgovt on Thursday January 12, 2023 @04:09PM
(#34360278)
> The URL bar shows the malicious site either way
That's never been sufficient to keep bad actors out because end-users don't grok the URL bar.
This attack is superior to a mirroring attack because it uses the target site's own UI resources, so it looks very legit (no need to pay someone to monitor the UI of the target site for changes and rework your exploit to attack them).
https://en.wikipedia.org/wiki/Framekiller
It's one of those situations where "This was mis-designed with insufficient eye towards how right bastards could use it, but the cat is out of the bag. We can't change the spec because it'll break legitimate uses of this technology, so this is the best option we have." Similar to how images were naively scoped to be embeddable from any web domain and then people invented pixel bugs, but you can't change the security model around image loading without breaking vast swathes of the existing web.