Comments on: JavaScript opens doors to browser-based attacks
Malicious code embedded in Web site can let miscreant map a home or corporate network, attack connected devices.
Malicious code embedded in Web site can let miscreant map a home or corporate network, attack connected devices.
January 2, 2010 6:26 PM PST
January 2, 2010 4:56 PM PST
January 2, 2010 4:16 PM PST
Add headlines from CNET News to your homepage or feedreader.
More feeds available in our RSS feed index.
Related quotes
I have been studying JavaScript extensively as part of my Web Development regime and am finding more and more way's to manipulate it for evil than for good! And you though cookies were harmless!
J Gund
Tech01
www.tech01.net
script attacks or was that just a poor choice on the graphic
artist's part?
to this kind of attack. All that's required is that the user has
JavaScript enabled on their browser. I'm sure that the choice of the
MacBook in the graphic was only because it looks cool, not because
Apple machines are any more or less affected by these kinds of
attacks than anyone else.
Users are having to accept patches to problems when they are wanting REAL solutions.
Society actualy cares, but is not able to cope with the ever increasing speed of tech and lack of knowledge of the same.
Maxi
sites, work just fine without Javascript. I think it makes
more sense to have Javascript turned off by default and then
only activate it when really necessary.
If you want to view a link... it can be done in HTML... no need to use Javascript... but many do.
Javascript looses readers... especially those like me because I don't allow javascript for just anybody. There must be a reason.
But if that reason is because some bloody javascript crazy programmer decided to use javascript rather than just plain HTML... then I don't view that site and I also voice my opinion against that site to all of my buddies.
Javascript needs to be used with care... only when required... not just when desired.
And if you haven't figured it out yet... I block ALL javascript by default. And must have sound reasoning why to unblock it.
Sadly however... much of the internet doesn't understand the vulnerabilites of it and thus programs javascript for everything.
Walt
Personally, my solution would be to improve both Javascript and browsers to keep abusers from doing any harm rather than disabling Javascript.
Hey, you drive to work, don't you? Would you rather walk to work instead because it's better for the environment? Or would you rather drive a more environment-friendly car such as a hybrid?
There are many many reasons for using javascript that have nothing that make it compelling to use, not to mention that it's a core piece of most of the main stream web development platforms.
I love how web users continually demonize technologies (usually based on a small amount of bad press) without any true understanding of what benefits those technologies provide. First it was "evil cookies", now it's "evil javascript".
Could the web be built without things like javascript and cookies? Absolutely, but it would be a lot less functional and sadly the same group of people would probably be the ones to complain about how non-user friendly many sites would become.
I'd prefer to keep things in perspecitve and not throw the baby out with the bathwater...
Seems to me a solution needs to be built into the browser rather than something external. For example, anytime a script attempts to do anything outside of a pre-defined security context, a confirmation dialog is received. This way if you want a script to log into your broadband router and turn off the firewall, you can let it. Perhaps the browser could also flag a site a "unsafe" if it trys anything funny.
Users of Windows Live OneCare are familiar with these kind of alerts - when an application attempts to access the Internet. Why not apply the same logic to the browser?
How difficult can it be to put a fence around a script (letting the user define its boundries) and require a user confirmation when action is initiated beyond that fence?
- The TRUTH about Firefox
- by umbrae July 31, 2006 6:54 AM PDT
- Disabling JavaScript in Firefox does, in fact, block this request. I have no experience with the NOSCRIPT "3rd Party" extension for Javascript, but this is a "3rd Party" tool and does not reflect upon any of the "core" Firefox development team. Regardless of what Google tools Mozilla decides to include in 2.0.
- Like this Reply to this comment
-
(29 Comments)Please understand how a browser works and is developed before you lay claims to what they do and do not know.
Once again, you can uncheck "Enable Javascript" in Firefox and it will block this exploit.