LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Advisory Watch: December 19th, 2014
Linux Advisory Watch: December 12th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
US-CERT uncovers JavaScript security vulnerability in Safari Print E-mail
User Rating:      How can I rate this item?
Source: CNET Reviews - Posted by Anthony Pell   
Security The United States Computer Emergency Readiness Team (US-CERT) has found a security hole in Safari, with which a hacker could run arbitrary code at the privilege level of the current user account if the victim visits a malicious Web page. Outlined Monday on the CERT Web site, this problem happens because Safari fails to properly handle references to window objects in the HTML DOM, and allows DOM window references to exist even if the corresponding window object has been deleted. The remaining reference pointer can be used by JavaScript to run code and be used to exploit the user. Apparently there are already public exploits available for this vulnerability.

So far the problem has been confirmed to be on the Windows version of Safari; however, it could also exist on the Mac.

There are no known fixes as yet, and it will be up to Apple to fix the problem fully with a Safari update. In the meantime, there are several things you can do to both reduce the potential harm from exploits of this vulnerability, as well as prevent it from being used.

  1. Use nonadministrative accounts. This vulnerability is only able to run code with the permissions of the current user on the system. If you are using an administrative account, then there is more potential for harm from an exploit.

Read this full article at CNET Reviews

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Report: U.S. planning “proportional response” to Sony hack, blamed on North Korea
Heartbleed, Shellshock, Tor and more: The 13 biggest security stories of 2014
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.