BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

Java Pwns Everyone…Again.

Posted August 30, 2012    BeyondTrust Research Team

Java has a nasty habit of getting you owned. This latest 0day is no exception to the long-lived trend of reliable Java-based exploitation. Here’s what you need to know:

How does it work?

The current exploitation method being employed in the wild right now leverages two zero day flaws in Java. The first flaw leverages an implementation issue (logic bug) within ClassFinder.findClass(), which is only present in Java 7. The method findClass() allows Java code to access restricted classes, when it should disallow such access. By using findClass() to gain access to restricted classes, the exploit is then able to use a reference for sun.awt.SunToolkit to access the getField() method. The second flaw, found in getField(), allows Java code to modify private fields (logic bug), which should normally be immutable when accessed externally (from outside the class it was declared in). The exploit uses getField() in order to modify the permissions of java.beans.Statement, which is then used to disable the Java Security Manager. At this point, the exploit is able to run code arbitrarily. No memory corruption occurs in the exploitation of these vulnerabilities. This makes the exploit 100% reliable for Java 7, across multiple platforms and through multiple browser-based attack vectors.

What can we do to mitigate this threat?

  1. Install the patch from Oracle for CVE-2012-4681.
  2. Audit your environment for systems that have Java. Determine what systems actually need Java and remove it according to your needs. Once you have reduced your Java footprint, you can further reduce your attack surface by restricting how Java runs; determine if a system needs Java for Internet facing applications or if it needs Java for desktop and internal applications. Configure systems that need Java granularly – more information on how to do this can be found in the links below.a. Controlling Java<Applet> Tags http://blogs.msdn.com/b/ieinternals/archive/2011/05/15/controlling-java-in-internet-explorer.aspx
    b. Controlling Java <Object> Tags (ActiveX) http://support.microsoft.com/kb/2751647

It is important to note that some security companies have incorrectly recommended mitigation strategies for Java which would only disable the loading of Java via Applet tags, but not via Object/ActiveX instantiation. To be blunt, if you had followed those recommendations, an attacker would have simply changed Applet tags to Object tags and owned your systems. So keep in mind when reviewing mitigations, even from “Quality” folks in the vulnerability management space, that your mileage may vary. ;-)

This constant panic over Java sucks…

Yes, yes it does. Java is a big, powerful, and widely used software package that is prone to gnarly vulnerabilities like the ones being exploited right now. As such, it will continue to garner a lot of attention from malicious entities. This exploit has already been folded into Metasploit and is being used actively in the BlackHole exploit kit. By limiting the use of Java within your organization, you’re effectively closing doors that attackers would otherwise stroll through. Following the aforementioned recommendations will help reduce the likelihood of exploitation and let you breathe a little easier.

BeyondTrust’s Retina Network Security Scanner (Retina Community is free) can audit for systems that are vulnerable to this issue:

17016 – Oracle Sun Java ClassFinder Vulnerability (CVE-2012-4681) – Windows – JDK
17017 – Oracle Sun Java ClassFinder Vulnerability (CVE-2012-4681) – Windows – JRE
17018 – Oracle Sun Java ClassFinder Vulnerability (CVE-2012-4681) – UNIX/Linux – JDK
17019 – Oracle Sun Java ClassFinder Vulnerability (CVE-2012-4681) – UNIX/Linux – JRE

 

Tags:
, , , , , , , ,

Leave a Reply

Additional articles

Restricted Area Sign

Implementing Least Privilege for Windows the Easy Way

Posted July 31, 2014    Morey Haber

The concept of least privilege states that asset users should have the lowest level of access privileges required to effectively conduct their jobs. Implementing least privilege can bring several benefits to your organization, including: Increased security by reducing the attack surface available to users and to potential attackers who compromise user systems via phishing, malware,…

Tags:
, , ,
gartner market guide image - aug 2014

Introducing the Gartner Market Guide for Privileged Account Management

Posted July 29, 2014    Chris Burd

Gartner recently released a new Market Guide for Privileged Account Management (PAM), and we’d like to share a complimentary copy with you. The report includes PAM market analysis and direction, vendor overviews, and recommendations for selecting PAM solutions for your environment. BeyondTrust is one of two representative vendors (out of 20) to address all solution…

Tags:
, , , , , , , ,
Integrating Least Privilege and Password Management to Solve Account Security Challenges

Integrating Least Privilege and Password Management to Solve Account Security Challenges

Posted July 24, 2014    Morey Haber

There is a reason all BeyondTrust Privileged Account Management (PAM) solutions share the PowerBroker name: They all inherently enable you to reduce user-based risk and can be integrated under a centralized IT risk management platform. Here’s one common use case that demonstrates how this integration changes the playing field. Consider the challenge of privileged access:…

Tags:
, , , , ,