A Security Vulnerability in the Java Runtime Environment may Allow Code Loaded From the Local Filesystem to Access LocalHost |
|
| Category : | Security |
| Release Phase : | Resolved |
| Bug Id : | 6704154
|
| Date of Resolved Release : | 03-Dec-2008
|
| Product : | Java Platform, Standard Edition 6 (Java SE 6)
|
A security vulnerability in the Java Runtime Environment may allow code loaded from the local filesystem to access localhost:
1. Impact
The Java Runtime Environment (JRE) allows code loaded from the local
filesystem to access localhost. This may allow code that is maliciously
placed on the local filesystem and then subsequently run, to have
network access to localhost that would not otherwise be allowed if the
code were loaded from a remote host. This may be leveraged to steal cookies and
hijack sessions (for domains that map a name to the localhost).
2. Contributing Factors
These issues can occur in the following Java SE and Java SE for
Business
releases for Solaris, Windows and Linux:
- JDK and JRE 6 Update 10 or earlier
- JDK and JRE 5.0 Update 16 or earlier
- SDK and JRE 1.4.2_18 or earlier
and the following Java SE releases for Solaris, Windows and Linux:
- SDK and JRE 1.3.1_23 and earlier
To determine the default version of the JRE that Internet Explorer uses:
- Click "Tools" in the Menu Bar at the top of the browser
- Select "Sun Java Console"
The first two lines
in the console display the version of Java Plug-in
and JRE that Internet Explorer uses.
To determine the default version of the JRE
that Mozilla or Firefox browsers use, visit the URL "about:plugins".
The browser
will display a page called "Installed plug-ins" which lists
the version of the Java Plug-in, as shown in the following example:
Java(TM) Plug-in 1.5.0_11-b03
(Indicating that the
JRE version the browser uses is 1.5.0_11)
3.
Symptoms
There are no reliable symptoms that would indicate the described issue
has been exploited.
4. Workaround
There is no workaround for this issue. Please see the Resolution
section below.
5. Resolution
This issue is addressed in the following Java SE and Java SE for
Business releases for Solaris, Windows and Linux:
- JDK and JRE 6 Update 11 or later
- JDK and JRE 5.0 Update 17 or later
- SDK and JRE 1.4.2_19 or later
and in the following Java SE releases for Solaris, Windows and Linux:
- SDK and JRE 1.3.1_24 or later
Java SE releases are available
at:
JDK 6 Update 11:
JRE 6 Update 11:
and through the
Java
Update
tool for Microsoft Windows users.
JDK 6 Update 11 is also available for Solaris in
the following patches:
- Java SE 6: update 11 (as delivered in patch 125136-12)
- Java SE 6: update 11 (as delivered in patch 125137-12 (64bit))
- Java SE 6_x86: update 11 (as delivered in patch 125138-12)
- Java SE 6_x86: update 11 (as delivered in patch 125139-12 (64bit))
JDK and JRE 5.0 Update 17:
JDK 5.0 Update 17
is also available for Solaris in
the following patches:
- J2SE 5.0: update 17 (as delivered in patch 118666-18)
- J2SE 5.0: update 17 (as delivered in patch 118667-18 (64bit))
- J2SE 5.0_x86: update 17 (as delivered in patch 118668-18)
- J2SE 5.0_x86: update 17 (as delivered in patch 118669-18 (64bit))
SDK and JRE 1.4.2_19:
Java SE for Business Releases:
Note 1: Java SE releases SDK
and JRE 1.4.2 have completed the Sun End of Service Life (EOSL)
process. Sun recommends that users upgrade to the latest Java SE
release. Customers interested in continuing to receive critical fixes
on SDK and JRE 1.4.2 are encouraged to migrate to
Java SE
for Business.
Note 2: SDK and JRE 1.3.1 have
completed the Sun End of Service Life (EOSL) process and is only
supported for customers with Solaris 8 and Vintage Support Offering
support contracts (see:
http://java.sun.com/j2se/1.3/download.html).
Sun strongly recommends that users upgrade to the latest Java SE
release.
Note 3: When installing a new
version of the product from a source other than a Solaris patch, it is
recommended that the old affected versions be removed from your system.
To remove old affected versions on the Windows platform, please see:
Note 4: Sites that require
applications loaded from filesystems to access localhost need to add
permissions in their "java.policy" file.
For more information
on Security Sun Alerts, see Technical
Instruction
ID 213557.
This Sun Alert notification is being provided to you on
an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU
ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT
OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This
Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements.
Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle,
Santa
Clara, CA 95054 U.S.A. All rights reserved.
AttachmentsThis solution has no attachment