exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

Java 1.7.0_21-b11 Code Execution

Java 1.7.0_21-b11 Code Execution
Posted Apr 22, 2013
Authored by Adam Gowdiak | Site security-explorations.com

Java versions 1.7.0_21-b11 and below suffers from an arbitrary code execution vulnerability.

tags | advisory, java, arbitrary, code execution
SHA-256 | 3158f404571528b94f1fbd702d6393ab7fee07d0e1316cf499dea137b946ebac

Java 1.7.0_21-b11 Code Execution

Change Mirror Download

Hello All,

Today, a vulnerability report with an accompanying Proof of
Concept code was sent to Oracle notifying the company of a
new security weakness affecting Java SE 7 software.

The new flaw was verified to affect all versions of Java SE
7 (including the recently released 1.7.0_21-b11). It can be
used to achieve a complete Java security sandbox bypass on
a target system. Successful exploitation in a web browser
scenario requires proper user interaction (a user needs to
accept the risk of executing a potentially malicious Java
application when a security warning window is displayed).

What's interesting is that the new issue is present not only
in JRE Plugin / JDK software, but also the recently announced
Server JRE as well [1]. Those concerned about a feasibility
of exploitation of Java flaws in a server environment should
consult Guideline 3-8 of "Secure Coding Guidelines for a Java
Programming Language" [2]. It lists the following software
components and APIs as potentially prone to the execution of
untrusted Java code:
- Sun implementation of the XSLT interpreter,
- Long Term Persistence of JavaBeans Components,
- RMI and LDAP (RFC 2713),
- Many SQL implementations.

In Apr 2012 [3], we reported our first vulnerability report
to Oracle corporation signaling multiple security problems in
Java SE 7 and the Reflection API in particular. It's been a
year since then and to our true surprise, we were still able
to discover one of the simplest and most powerful instances
of Java Reflection API based vulnerabilities. It looks Oracle
was primarily focused on hunting down potentially dangerous
Reflection API calls in the "allowed" classes space. If so,
no surprise that Issue 61 was overlooked.

Thank you.

Best Regards
Adam Gowdiak

---------------------------------------------
Security Explorations
http://www.security-explorations.com
"We bring security research to the new level"
---------------------------------------------

References:
[1] Server JRE (Java SE Runtime Environment) 7 Downloads

http://www.oracle.com/technetwork/java/javase/downloads/server-jre7-downloads-1931105.html
[2] Secure Coding Guidelines for the Java Programming Language, Version 4.0
http://www.oracle.com/technetwork/java/seccodeguide-139067.html
[3] SE-2012-01 Vendors status
http://www.security-explorations.com/en/SE-2012-01-status.html
Login or Register to add favorites

File Archive:

April 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    10 Files
  • 2
    Apr 2nd
    26 Files
  • 3
    Apr 3rd
    40 Files
  • 4
    Apr 4th
    6 Files
  • 5
    Apr 5th
    26 Files
  • 6
    Apr 6th
    0 Files
  • 7
    Apr 7th
    0 Files
  • 8
    Apr 8th
    22 Files
  • 9
    Apr 9th
    14 Files
  • 10
    Apr 10th
    10 Files
  • 11
    Apr 11th
    13 Files
  • 12
    Apr 12th
    14 Files
  • 13
    Apr 13th
    0 Files
  • 14
    Apr 14th
    0 Files
  • 15
    Apr 15th
    30 Files
  • 16
    Apr 16th
    10 Files
  • 17
    Apr 17th
    22 Files
  • 18
    Apr 18th
    45 Files
  • 19
    Apr 19th
    0 Files
  • 20
    Apr 20th
    0 Files
  • 21
    Apr 21st
    0 Files
  • 22
    Apr 22nd
    0 Files
  • 23
    Apr 23rd
    0 Files
  • 24
    Apr 24th
    0 Files
  • 25
    Apr 25th
    0 Files
  • 26
    Apr 26th
    0 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close