Yes. One is the recursive @import I mentioned and
the other requires script:
http://technet.microsoft.com/en-us/security/bulletin/MS10-090
Virtually all exploits require script. The recursive @import
doesn't, but that's a browser bug, not a CSS vulnerability.
Since CSS and HTML only specify graphical display details
it's hard to see how they can be directly vulnerable. Script,
on the other hand, is executable code. It's nearly impossible
to make it reasonably safe. (Java and Flash have both
become big problems lately, despite years of claims that
they were safe.) *Executable code is not safe. Period.*
|
| > If you can't trust PayPal to keep their site clean then
| > who can you trust?
|
| Nobody as it seems - if you put it this way...
|
| But then, on the other hand - there's billions of
| (successful) transactions done over all the different
| banking-sites world-wide - most of them requiring an
| enabled JS-engine in the Browser.
|
You were saying that the reasonable
approach is to assign a level of trust to sites and
act accordingly. I'm just pointing out that such an
approach is more hopeful than practical.
| And here's perhaps, where we disagree - with your:
| "all bets are off" you make it sound like "better not
| go outside when it starts raining, because you could
| be struck by lightning".
No. Once again you're trying to cast my position as
all-or-nothing paranoia. All bets are off meant that once
script is involved there's no way to act safely. One can
keep updated with all security patches, run a firewall,
etc. All of that *might* help. But none can make for
dependable safety. The fact that a large percentage of
web pages are safe is a red herring.
| One could be hit of course ... according to wikipedia:
| "An estimated 24,000 people are killed by lightning strikes
| around the world each year and about 240,000 are injured"
| but it's not very probable.
|
http://en.wikipedia.org/wiki/Lightning_strike
|
Again, a red herring. We're talking about browser use
online, not lightning strikes. (Though I should probably add
a disclaimer here: I have a brother who installs lightning
protection systems. :)
| But your recommendation, to surf "by default" with a disabled
| JS-engine these days, borders on the recommendation, to drive
| not faster than 10mph
I've never seen you so heated about a topic. I do
nearly all browsing with script blocked. I don't have
Flash or Java installed. I block 3rd-party images and
IFRAMES. While I deal with some ugly pages as a result,
I also avoid most tracking, 3rd-party ads, and risks.
And I don't see 3 videos playing while I'm trying to
read an article. To me those are all plusses.
The only page I regularly visit that requires script is
a TV schedule website. I use Firefox for that and Pale
Moon for all other browsing. I read lots of news and tech.
sites with no problem. I also visit virtually all programming
sites without problem, except for the ones that require
membership, like CodeProject. (One exception is Eduardo
Morcillo's website. His has been a dysfunctional mess of
frivolous script for years.... but he also no longer deals with
VB, so that doesn't really matter.) I occasionally go to Youtube,
but with DownloadHelper I can save a copy of video without
needing to play it or enable script. ...So why in the world
would I add unnecessary risk? (I should add, though, that
I also don't use webmail, Facebook, etc. For some people,
no script would, indeed, mean no Internet.)
| And then on my small experimental site, dedicated to developers,
| (with more than "average web-knowledge") I should try to avoid it,
| to not put my poor fellow colleagues at risk?
| Nahhh... ;-)
|
| Web-Content is getting more an more dependent on "clientside
| dynamics"
I think it's worth getting people to think about these
issues, and you're willing to talk about it. So I pursued
it. But it is, of course, up to you. For my part I'll never
see your website. I'm perfectly happy with an Internet
that works like a magazine with downloads. (And doesn't
require AV, Malwarebytes, or Microsoft's patch drip-feed.)
And to my mind most of what is out there with script and
Flash enabled looks like a garish TV playing the Crazy
Eddie Channel.
I think the future inevitability is the reverse
of the way you see it. Interactivity is heavily hyped and
marketed because it's a lucrative business model. But we
can't keep increasing interactivity and risk in an open
marketplace. There will have to be new security systems
that work privately. And as we head into a world that's
almost entirely electronic, where personal relationships and
reputation count for almost nothing, we're headed into
uncharted territory. If you want to venture into that
thunderstorm it wouldn't hurt to at least put some shoes on.
I saw an interesting comment recently from Ben Affleck
about making Argo. He said that he toured the CIA offices
and saw that each agent had 2 PCs. One for online and one
for internal. And there was an interesting piece on Slashdot
last week about a search engine that can lead to all sorts
of online, unsecured computers, including the controls for
nuclear power plants:
http://search.slashdot.org/story/13/04/09/1828230/the-search-engine-more-dangerous-than-google
This is not a case of increasing Internet interactivity being
inevitable. Rather, it's a case of a relatively new technology
that still has some very big wrinkles to be ironed out; a new
technology that people have been overly cavalier about.