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 MichaelDavidCrawford on Thursday March 01 2018, @12:52AM (2 children)
A while back I was amused to discover that the parking pages employed by domain speculators often included a favicon.ico that was full of javascript.
I'd really like to see all the browsers enforce ico-ness on favicon.ico. There's no damn good reason that a browser should load javascript from it.
Yes I Have No Bananas. [gofundme.com]
(Score: 0) by Anonymous Coward on Thursday March 01 2018, @04:12PM (1 child)
How else are we going to be able to make it do its spinny thing?
(Score: 2) by Pino P on Thursday March 01 2018, @10:18PM
<link rel="icon" href="/favicon.gif">