MAAS History
Archives
Friday
Apr032009

Microsoft Office PowerPoint Remote Code Execution

This affects MS Office SP3 2000, 2002, 2003 and MS Office 2004 Mac. An attacker can gain access to the user rights of systems running Microsoft Office Mac 2004 using specially crafted content in a PowerPoint document. This can be accomplished by sending the file to a unsuspecting user or downloading it from a site. The attacker can behave as the compromised user.

Again, user education is key to preventing this kind of attack. Only open documents from trusted sources, use MOICE (Windows OS) and do not open earlier versions of MS Office files. Since Office files are .ZIP files containing meta and content data it is important that trust policies be reiterated to users, namely if an Office document comes from an unknown source do not open it. This is also true of ICal files, mail, QT, etc. Never perform task such as email, office activities or web surfing as a system administrator or root. 

No updates at this time, see MS reference article attached for mitigation options.

Friday
Mar272009

OpenSSL Vulnerabilities 

What are considered moderate vulnerabilities in SSL/TLS which e-commerce sites and other sites using OpenSSL it is possible to cause a DoS attack by causing OpenSSL to crash. 

 

  1. ASN1 Printing Crash- CVE-2009-0590
  2. Incorrect Error Checking During CMS verification- CVE-2009-0591
  3. Invalid ASN1 clearing check- CVE-2009-00789

 

Friday
Mar272009

Firefox Zero day in the Wild

Guido Landi has discovered a security flaw in Firefox to parse an particular XSL element. Windows and Linux are the platforms affected but it is safe to say that the Mac may be also be vulnerable. That nice thing is that a patch is availably, make sure to update to the latest version of Firefox.

Thursday
Mar192009

Pwn2Own, Safari First to Fall

Charlie Miller, a security researcher, used an exploit that he had discovered and perfected last year. If a user clicks on a malicious URL, an attacker can gain access and exploit the users machine, I have not found out if the attack is root or user sand boxed. Luckily this information will be shared with Apple but it addresses a very important point. Macintosh's can be exploited by drive by web attacks, we have also seen this with QuickTime, ICal, Acrobat etc. First up no user should be operating as the administrator when performing user level task including web surfing, email, word processing, etc.  

Make sure policies and procedures about visiting web sites are reviewed and users are not lured into a false sense of security. Education of users and strict policies about administrators and root activity are very important in defending against these kinds of attacks. Network administrators should also update their white and black list of sites (This is always good to reveiw) and review application level proxies, especially at the network boundaries. As with any network, egress filtering of traffic is very important to securing your Macintosh infrastructure. Knowing what is going out is as important to knowing what is coming in. 

Hey baby, it's Unix the beast }:-> 

 

Thursday
Mar122009

Zero Day: Acrobate Reader Still Out There

Adobe's current fix does not fix the actual vulnerability but you should update to version 9.1. At the firewall level it may be prudent to block PDF's from un-trusted sources. The Zero Day PDF has malicious code that can exploit a buffer overflow allowing execution of code on your system. First up you should not have JavaScript enabled, if it is disable it right away. This exploit may crash Reader if you disable JavaScript but it will be unable to install the malicious code onto your system. 

One important aspect of defense against this exploit is education of users, make sure to review attachment policies and procedures. Users should not open any documents from un-trusted or unknown sources. (Make sure that your policies and procedures give users clear guidance including case examples.) Trust and un-trusted sources can be filtered at the external fire wall which you should be doing already. 

 

CVE number: CVE-2009-0658