Headline
CVE-2012-1717: Oracle Java SE Critical Patch Update Advisory - June 2012
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 update 32 and earlier, 5 update 35 and earlier, and 1.4.2_37 and earlier allows local users to affect confidentiality via unknown vectors related to printing on Solaris or Linux.
Click to view our Accessibility Policy
Skip to content
Security Alerts
Oracle Java SE Critical Patch Update Advisory - June 2012****Description
A Critical Patch Update is a collection of patches for multiple security vulnerabilities. The Critical Patch Update for Java SE also includes non-security fixes. Critical Patch Updates are cumulative and each advisory describes only the security fixes added since the previous Critical Patch Update. Thus, prior Critical Patch Update Advisories should be reviewed for information regarding earlier accumulated security fixes. Please refer to:
Critical Patch Updates and Security Alerts for information about Oracle Security Advisories.
Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible. This Critical Patch Update contains 14 new security fixes across Java SE products.
Supported Products Affected
Security vulnerabilities addressed by this Critical Patch Update affect the products listed in the categories below. Please click on the link in the Patch Availability column or in the Patch Availability Table to access the documentation for those patches.
Affected product releases and versions:
Java SE
Patch Availability
JDK and JRE 7 Update 4 and earlier
Java SE
JDK and JRE 6 Update 32 and earlier
Java SE
JDK and JRE 5.0 Update 35 and earlier
Java SE
SDK and JRE 1.4.2_37 and earlier
Java SE
JavaFX 2.1 and earlier
JavaFX
Patch Availability Table and Risk Matrix
Java SE fixes in this Update are cumulative; the latest Critical Patch Update includes all fixes from the previous Critical Patch Updates.
Patch Availability Table****Risk Matrix Content
The risk matrix lists only security vulnerabilities that are newly fixed by the patches associated with this advisory. Risk matrices for previous security fixes can be found in previous Critical Patch Update advisories.
Security vulnerabilities are scored using CVSS version 2.0 (see Oracle CVSS Scoring for an explanation of how Oracle applies CVSS 2.0). Oracle conducts an analysis of each security vulnerability addressed by a Critical Patch Update (CPU). Oracle does not disclose information about the security analysis, but the resulting Risk Matrix and associated documentation provide information about the type of vulnerability, the conditions required to exploit it, and the potential result of a successful exploit. Oracle provides this information, in part, so that customers may conduct their own risk analysis based on the particulars of their product usage. As a matter of policy, Oracle does not disclose detailed information about an exploit condition or results that can be used to conduct a successful exploit. Oracle will not provide additional information about the specifics of vulnerabilities beyond what is provided in the CPU or Security Alert notification, the Patch Availability Document, the readme files, and FAQs. Oracle does not provide advance notification on CPUs or Security Alerts to individual customers. Finally, Oracle does not distribute exploit code or “proof-of-concept” code for product vulnerabilities.
Workarounds
Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible. Until you apply the CPU fixes, it may be possible to reduce the risk of successful attack by restricting network protocols required by an attack. For attacks that require certain privileges or access to certain packages, removing the privileges or the ability to access the packages from unprivileged users may help reduce the risk of successful attack. Both approaches may break application functionality, so Oracle strongly recommends that customers test changes on non-production systems. Neither approach should be considered a long-term solution as neither corrects the underlying problem.
Skipped Critical Patch Updates
Oracle strongly recommends that customers apply fixes as soon as possible. For customers that have skipped one or more Security advisories, please review previous advisories to determine appropriate actions.
Unsupported Products and De-Supported Versions
Unsupported products, releases and versions are not tested for the presence of vulnerabilities addressed by this Critical Patch Update. However, it is likely that earlier versions of affected releases are also affected by these vulnerabilities. Hence Oracle recommends that customers upgrade their Oracle products to a supported version.
Critical Patch Update patches are not provided for product versions that are no longer supported. We recommend that customers upgrade to the latest supported version of Oracle products in order to obtain patches.
Credit Statement
The following people or organizations reported security vulnerabilities addressed by this Critical Patch Update to Oracle: Adam Gowdiak of Security Explorations; Andrei Costin via Secunia; Chris Ries via TippingPoint; and Clayton Smith of Entrust.
Oracle Java SE Critical Patch Update Schedule
The next three dates for Oracle Java SE Critical Patch Updates are:
- 16 October 2012
- 19 February 2013
- 18 June 2013
References
- Oracle Critical Patch Updates and Security Alerts main page [ Oracle Technology Network ]
- Oracle Critical Patch Updates and Security Alerts - Frequently Asked Questions [ CPU FAQ ]
- Risk Matrix definitions [ Risk Matrix Definitions ]
- Use of Common Vulnerability Scoring System (CVSS) by Oracle [ Oracle CVSS Scoring ]
- English text version of risk matrices [ Oracle Technology Network ]
- Previous Security Advisories for Java SE Security Updates [ Java Sun Alerts Archive Page ]
Modification History
Date
Comments
2012-June-12
Rev 1. Initial Release
Appendix - Oracle Java SE****Oracle Java SE Executive Summary
This Critical Patch Update contains 14 new security fixes for Oracle Java SE. 12 of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without the need for a username and password. The English text form of this Risk Matrix can be found here.
The CVSS scores below assume that a user running a Java applet or Java Web Start application has administrator privileges (typical on Windows). When the user does not run with administrator privileges (typical on Solaris and Linux), the corresponding CVSS impact scores for Confidentiality, Integrity, and Availability are “Partial” instead of "Complete", lowering the CVSS Base Score. For example, a Base Score of 10.0 becomes 7.5.
For issues in Deployment, fixes are only made available for JDK and JRE 7 and 6. Users should use the default Java Plug-in and Java Web Start in the latest JDK and JRE 7 or 6 releases.
My Oracle Support Note 360870.1 explains the impact of Java security vulnerabilities on Oracle products that include an Oracle Java SE JDK or JRE.
Oracle Java SE Risk Matrix
CVE#
Component
Protocol
Sub- component
Remote Exploit without Auth.?
CVSS VERSION 2.0 RISK (see Risk Matrix Definitions)
Supported Versions Affected
Notes
Base Score
Access Vector
Access Complexity
Authen- tication
Confiden- tiality
Integrity
Avail- ability
CVE-2012-1713
Java Runtime Environment
Multiple
2D
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before. JavaFX 2.1 and before
See Note 1
CVE-2012-1721
Java Runtime Environment
Multiple
Deployment
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before
See Note 2
CVE-2012-1722
Java Runtime Environment
Multiple
Deployment
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before
See Note 2
CVE-2012-1723
Java Runtime Environment
Multiple
Hotspot
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 2
CVE-2012-1725
Java Runtime Environment
Multiple
Hotspot
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before
See Note 2
CVE-2012-1716
Java Runtime Environment
Multiple
Swing
Yes
10.0
Network
Low
None
Complete
Complete
Complete
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before
See Note 2
CVE-2012-1711
Java Runtime Environment
Multiple
CORBA
Yes
7.5
Network
Low
None
Partial
Partial
Partial
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 2
CVE-2012-1726
Java Runtime Environment
Multiple
Libraries
Yes
6.4
Network
Low
None
Partial
Partial
None
7 Update 4 and before
See Note 2
CVE-2012-0551
Java Runtime Environment
Multiple
Deployment
Yes
5.8
Network
Medium
None
Partial
None
Partial
7 Update 4 and before, 6 Update 32 and before
See Note 2
CVE-2012-1719
Java Runtime Environment
Multiple
CORBA
Yes
5.0
Network
Low
None
None
Partial
None
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 2
CVE-2012-1724
Java Runtime Environment
Multiple
JAXP
Yes
5.0
Network
Low
None
None
None
Partial
7 Update 4 and before, 6 Update 32 and before
See Note 1
CVE-2012-1718
Java Runtime Environment
Multiple
Security
Yes
5.0
Network
Low
None
None
None
Partial
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 1
CVE-2012-1720
Java Runtime Environment
Multiple
Networking
No
3.7
Local
High
None
Partial
Partial
Partial
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 3
CVE-2012-1717
Java Runtime Environment
Multiple
Java Runtime Environment
No
2.1
Local
Low
None
Partial
None
None
7 Update 4 and before, 6 Update 32 and before, 5 Update 35 and before, 1.4.2_37 and before
See Note 4
Notes:
- Applies to client and server deployment of Java. This vulnerability can be exploited through untrusted Java Web Start applications and untrusted Java applets. It can also be exploited by supplying data to APIs in the specified Component without using untrusted Java Web Start applications or untrusted Java applets, such as through a web service.
- Applies to client deployment of Java only. This vulnerability can be exploited only through untrusted Java Web Start applications and untrusted Java applets. (Untrusted Java Web Start applications and untrusted applets run in the Java sandbox with limited privileges.)
- Applies to server deployment of Java on Solaris only.
- Applies to printing on the Solaris and Linux platforms. This vulnerability cannot be exploited through untrusted Java Web Start applications or untrusted Java applets. It also cannot be exploited by supplying data to APIs in the specified Component without using untrusted Java Web Start applications or untrusted Java applets, such as through a web service.
Why Oracle
- Analyst Reports
- Best cloud-based ERP
- Cloud Economics
- Corporate Responsibility
- Diversity and Inclusion
- Security Practices
Learn
- What is cloud computing?
- What is CRM?
- What is Docker?
- What is Kubernetes?
- What is Python?
- What is SaaS?
What’s New
News
Oracle Applications Platform
Oracle Supports Ukraine
Oracle Red Bull Racing
Oracle Sustainability
Employee Experience Platform
© 2022 Oracle
Privacy/Do Not Sell My Info
Ad Choices
Careers
Related news
Hello everyone! On the last day of September, I decided to record another retrospective episode on how my Vulnerability Management month went. Alternative video link (for Russia): https://vk.com/video-149273431_456239136 September was quite a busy month for me. Vulnerability Management courses I participated in two educational activities. The first one is an on-line cyber security course for […]
New research shows that 57 vulnerabilities that threat actors are currently using in ransomware attacks enable everything from initial access to data theft.
Unspecified vulnerability in Oracle MySQL Server 5.1.62 and earlier and 5.5.23 and earlier allows remote authenticated users to affect availability, related to GIS Extension.
Unspecified vulnerability in Oracle MySQL Server 5.1.62 and earlier and 5.5.23 and earlier allows remote authenticated users to affect availability, related to GIS Extension.
Unspecified vulnerability in Oracle MySQL Server 5.1.62 and earlier and 5.5.23 and earlier allows remote authenticated users to affect availability, related to GIS Extension.
Unspecified vulnerability in Oracle MySQL Server 5.1.62 and earlier and 5.5.23 and earlier allows remote authenticated users to affect availability, related to GIS Extension.
Unspecified vulnerability in Oracle MySQL Server 5.1.62 and earlier and 5.5.23 and earlier allows remote authenticated users to affect availability, related to GIS Extension.
Unspecified vulnerability in the MySQL Server component in Oracle MySQL 5.1.61 and earlier, and 5.5.21 and earlier, allows remote authenticated users to affect availability via unknown vectors related to Server Optimizer, a different vulnerability than CVE-2012-1703.