Jake Archibald writes in his blog about the bigger problem presented by importing third-party content into web pages. Even CSS is a problem as a CSS keylogger demo showed the other day.
A few days ago there was a lot of chatter about a 'keylogger' built in CSS.
Some folks called for browsers to 'fix' it. Some folks dug a bit deeper and saw that it only affected sites built in React-like frameworks, and pointed the finger at React. But the real problem is thinking that third party content is 'safe'.
While most are acutely aware, yet ignore, the danger presentd by third-party javascript and javascript in general, most forget about CSS. Jake reminds us and walks through quite a few exampled of how CSS can be misused by third-parties exporting it.
Source : Third party CSS is not safe
(Score: 2) by julian on Wednesday February 28 2018, @11:33PM (1 child)
That's brilliant and terrifying.
The web was a mistake.
(Score: 2) by FatPhil on Thursday March 01 2018, @10:09AM
It was introduced in CSS2, and fixed in CSS2.1
And now they brought it back, because repeating mistakes is hilarious.
https://blog.mozilla.org/security/2010/03/31/plugging-the-css-history-leak/
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves