The version of Oracle (formerly Sun) Java SE or Java for Business installed on the remote host is prior to 8 Update 121, 7 Update 131, or 6 Update 141. It is, therefore, affected by multiple vulnerabilities :

  - A vulnerability exists in the Libraries subcomponent,     known as SWEET32, in the 3DES and Blowfish algorithms     due to the use of weak 64-bit block ciphers by default.
    A man-in-the-middle attacker who has sufficient     resources can exploit this vulnerability, via a     'birthday' attack, to detect a collision that leaks the     XOR between the fixed secret and a known plaintext,     allowing the disclosure of the secret text, such as     secure HTTPS cookies, and possibly resulting in the     hijacking of an authenticated session. (CVE-2016-2183)

  - An unspecified flaw exists in the Libraries subcomponent     that allows an unauthenticated, remote attacker to     impact integrity. (CVE-2016-5546)

  - An unspecified flaw exists in the Libraries subcomponent     that allows an unauthenticated, remote attacker to cause     a denial of service condition. (CVE-2016-5547)

  - Multiple unspecified flaws exist in the Libraries     subcomponent that allow an unauthenticated, remote     attacker to disclose sensitive information.
    (CVE-2016-5548, CVE-2016-5549)

  - An unspecified flaw exists in the Networking     subcomponent that allows an unauthenticated, remote     attacker to impact integrity. (CVE-2016-5552)

  - An unspecified flaw exists in the Mission Control     subcomponent that allows an unauthenticated, remote     attacker to impact integrity. (CVE-2016-8328)

  - Multiple unspecified flaws exist in the Networking     subcomponent that allow an unauthenticated, remote     attacker to disclose sensitive information.
    (CVE-2017-3231, CVE-2017-3261)

  - An unspecified flaw exists in the RMI subcomponent that     allows an unauthenticated, remote attacker to execute     arbitrary code. (CVE-2017-3241)

  - An unspecified flaw exists in the JAAS subcomponent that     allows an unauthenticated, remote attacker to impact     integrity. (CVE-2017-3252)

  - An unspecified flaw exists in the 2D subcomponent that     allows an unauthenticated, remote attacker to cause a     denial of service condition. (CVE-2017-3253)

  - An unspecified flaw exists in the Deployment     subcomponent that allows an unauthenticated, remote     attacker to disclose sensitive information.
    (CVE-2017-3259)

  - An unspecified flaw exists in the AWT subcomponent that     allows an unauthenticated, remote attacker to execute     arbitrary code. (CVE-2017-3260)

  - An unspecified flaw exists in the Java Mission Control     subcomponent that allows an unauthenticated, remote     attacker to disclose sensitive information.
    (CVE-2017-3262)

  - An unspecified flaw exists in the Libraries subcomponent     that allows an unauthenticated, remote attacker to     execute arbitrary code. (CVE-2017-3272)

  - An unspecified flaw exists in the Hotspot subcomponent     that allows an unauthenticated, remote attacker to     execute arbitrary code. (CVE-2017-3289)

Note that CVE-2017-3241 can only 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.
Note that CVE-2016-2183, CVE-2016-5546, CVE-2016-5547, CVE-2016-5552, CVE-2017-3252, and CVE-2017-3253 can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. They can also be exploited by supplying data to APIs in the specified component without using sandboxed Java Web Start applications or sandboxed Java applets, such as through a web service.

According to the versions of the java-1.8.0-openjdk packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - It was discovered that the RMI registry and DCG     implementations in the RMI component of OpenJDK     performed deserialization of untrusted inputs. A remote     attacker could possibly use this flaw to execute     arbitrary code with the privileges of RMI registry or a     Java RMI application. (CVE-2017-3241)

  - Multiple flaws were discovered in the Libraries and     Hotspot components in OpenJDK. An untrusted Java     application or applet could use these flaws to     completely bypass Java sandbox restrictions.
    (CVE-2017-3272, CVE-2017-3289)

  - A covert timing channel flaw was found in the DSA     implementation in the Libraries component of OpenJDK. A     remote attacker could possibly use this flaw to extract     certain information about the used key via a timing     side channel. (CVE-2016-5548)

  - It was discovered that the Libraries component of     OpenJDK accepted ECSDA signatures using non-canonical     DER encoding. This could cause a Java application to     accept signature in an incorrect format not accepted by     other cryptographic tools. (CVE-2016-5546)

  - It was discovered that the 2D component of OpenJDK     performed parsing of iTXt and zTXt PNG image chunks     even when configured to ignore metadata. An attacker     able to make a Java application parse a specially     crafted PNG image could cause the application to     consume an excessive amount of memory. (CVE-2017-3253)

  - It was discovered that the Libraries component of     OpenJDK did not validate the length of the object     identifier read from the DER input before allocating     memory to store the OID. An attacker able to make a     Java application decode a specially crafted DER input     could cause the application to consume an excessive     amount of memory. (CVE-2016-5547)

  - It was discovered that the JAAS component of OpenJDK     did not use the correct way to extract user DN from the     result of the user search LDAP query. A specially     crafted user LDAP entry could cause the application to     use an incorrect DN. (CVE-2017-3252)

  - It was discovered that the Networking component of     OpenJDK failed to properly parse user info from the     URL. A remote attacker could cause a Java application     to incorrectly parse an attacker supplied URL and     interpret it differently from other applications     processing the same URL. (CVE-2016-5552)

  - Multiple flaws were found in the Networking components     in OpenJDK. An untrusted Java application or applet     could use these flaws to bypass certain Java sandbox     restrictions. (CVE-2017-3261, CVE-2017-3231)

  - A flaw was found in the way the DES/3DES cipher was     used as part of the TLS/SSL protocol. A     man-in-the-middle attacker could use this flaw to     recover some plaintext data by capturing large amounts     of encrypted traffic between TLS/SSL server and client     if the communication used a DES/3DES based ciphersuite.
    (CVE-2016-2183)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update for java-1.8.0-openjdk is now available for Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

The java-1.8.0-openjdk packages provide the OpenJDK 8 Java Runtime Environment and the OpenJDK 8 Java Software Development Kit.

Security Fix(es) :

* It was discovered that the RMI registry and DCG implementations in the RMI component of OpenJDK performed deserialization of untrusted inputs. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application. (CVE-2017-3241)

This issue was addressed by introducing whitelists of classes that can be deserialized by RMI registry or DCG. These whitelists can be customized using the newly introduced sun.rmi.registry.registryFilter and sun.rmi.transport.dgcFilter security properties.

* Multiple flaws were discovered in the Libraries and Hotspot components in OpenJDK. An untrusted Java application or applet could use these flaws to completely bypass Java sandbox restrictions.
(CVE-2017-3272, CVE-2017-3289)

* A covert timing channel flaw was found in the DSA implementation in the Libraries component of OpenJDK. A remote attacker could possibly use this flaw to extract certain information about the used key via a timing side channel. (CVE-2016-5548)

* It was discovered that the Libraries component of OpenJDK accepted ECSDA signatures using non-canonical DER encoding. This could cause a Java application to accept signature in an incorrect format not accepted by other cryptographic tools. (CVE-2016-5546)

* It was discovered that the 2D component of OpenJDK performed parsing of iTXt and zTXt PNG image chunks even when configured to ignore metadata. An attacker able to make a Java application parse a specially crafted PNG image could cause the application to consume an excessive amount of memory. (CVE-2017-3253)

* It was discovered that the Libraries component of OpenJDK did not validate the length of the object identifier read from the DER input before allocating memory to store the OID. An attacker able to make a Java application decode a specially crafted DER input could cause the application to consume an excessive amount of memory. (CVE-2016-5547)

* It was discovered that the JAAS component of OpenJDK did not use the correct way to extract user DN from the result of the user search LDAP query. A specially crafted user LDAP entry could cause the application to use an incorrect DN. (CVE-2017-3252)

* It was discovered that the Networking component of OpenJDK failed to properly parse user info from the URL. A remote attacker could cause a Java application to incorrectly parse an attacker supplied URL and interpret it differently from other applications processing the same URL. (CVE-2016-5552)

* Multiple flaws were found in the Networking components in OpenJDK.
An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. (CVE-2017-3261, CVE-2017-3231)

* A flaw was found in the way the DES/3DES cipher was used as part of the TLS /SSL protocol. A man-in-the-middle attacker could use this flaw to recover some plaintext data by capturing large amounts of encrypted traffic between TLS/SSL server and client if the communication used a DES/3DES based ciphersuite. (CVE-2016-2183)

This update mitigates the CVE-2016-2183 issue by adding 3DES cipher suites to the list of legacy algorithms (defined using the jdk.tls.legacyAlgorithms security property) so they are only used if connecting TLS/SSL client and server do not share any other non-legacy cipher suite.

Note: If the web browser plug-in provided by the icedtea-web package was installed, the issues exposed via Java applets could have been exploited without user interaction if a user visited a malicious website.

Security Fix(es) :

  - It was discovered that the RMI registry and DCG     implementations in the RMI component of OpenJDK     performed deserialization of untrusted inputs. A remote     attacker could possibly use this flaw to execute     arbitrary code with the privileges of RMI registry or a     Java RMI application. (CVE-2017-3241)

This issue was addressed by introducing whitelists of classes that can be deserialized by RMI registry or DCG. These whitelists can be customized using the newly introduced sun.rmi.registry.registryFilter and sun.rmi.transport.dgcFilter security properties.

  - Multiple flaws were discovered in the Libraries and     Hotspot components in OpenJDK. An untrusted Java     application or applet could use these flaws to     completely bypass Java sandbox restrictions.
    (CVE-2017-3272, CVE-2017-3289)

  - A covert timing channel flaw was found in the DSA     implementation in the Libraries component of OpenJDK. A     remote attacker could possibly use this flaw to extract     certain information about the used key via a timing side     channel. (CVE-2016-5548)

  - It was discovered that the Libraries component of     OpenJDK accepted ECSDA signatures using non-canonical     DER encoding. This could cause a Java application to     accept signature in an incorrect format not accepted by     other cryptographic tools. (CVE-2016-5546)

  - It was discovered that the 2D component of OpenJDK     performed parsing of iTXt and zTXt PNG image chunks even     when configured to ignore metadata. An attacker able to     make a Java application parse a specially crafted PNG     image could cause the application to consume an     excessive amount of memory. (CVE-2017-3253)

  - It was discovered that the Libraries component of     OpenJDK did not validate the length of the object     identifier read from the DER input before allocating     memory to store the OID. An attacker able to make a Java     application decode a specially crafted DER input could     cause the application to consume an excessive amount of     memory. (CVE-2016-5547)

  - It was discovered that the JAAS component of OpenJDK did     not use the correct way to extract user DN from the     result of the user search LDAP query. A specially     crafted user LDAP entry could cause the application to     use an incorrect DN. (CVE-2017-3252)

  - It was discovered that the Networking component of     OpenJDK failed to properly parse user info from the URL.
    A remote attacker could cause a Java application to     incorrectly parse an attacker supplied URL and interpret     it differently from other applications processing the     same URL. (CVE-2016-5552)

  - Multiple flaws were found in the Networking components     in OpenJDK. An untrusted Java application or applet     could use these flaws to bypass certain Java sandbox     restrictions. (CVE-2017-3261, CVE-2017-3231)

  - A flaw was found in the way the DES/3DES cipher was used     as part of the TLS/SSL protocol. A man-in-the-middle     attacker could use this flaw to recover some plaintext     data by capturing large amounts of encrypted traffic     between TLS/SSL server and client if the communication     used a DES/3DES based ciphersuite. (CVE-2016-2183)

This update mitigates the CVE-2016-2183 issue by adding 3DES cipher suites to the list of legacy algorithms (defined using the jdk.tls.legacyAlgorithms security property) so they are only used if connecting TLS/SSL client and server do not share any other non-legacy cipher suite.

Note: If the web browser plug-in provided by the icedtea-web package was installed, the issues exposed via Java applets could have been exploited without user interaction if a user visited a malicious website.

It was discovered that the RMI registry and DCG implementations in the RMI component of OpenJDK performed deserialization of untrusted inputs. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application. (CVE-2017-3241) This issue was addressed by introducing whitelists of classes that can be deserialized by RMI registry or DCG.
These whitelists can be customized using the newly introduced sun.rmi.registry.registryFilter and sun.rmi.transport.dgcFilter security properties.

Multiple flaws were discovered in the Libraries and Hotspot components in OpenJDK. An untrusted Java application or applet could use these flaws to completely bypass Java sandbox restrictions. (CVE-2017-3272 , CVE-2017-3289)

A covert timing channel flaw was found in the DSA implementation in the Libraries component of OpenJDK. A remote attacker could possibly use this flaw to extract certain information about the used key via a timing side channel. (CVE-2016-5548)

It was discovered that the Libraries component of OpenJDK accepted ECSDA signatures using non-canonical DER encoding. This could cause a Java application to accept signature in an incorrect format not accepted by other cryptographic tools. (CVE-2016-5546)

It was discovered that the 2D component of OpenJDK performed parsing of iTXt and zTXt PNG image chunks even when configured to ignore metadata. An attacker able to make a Java application parse a specially crafted PNG image could cause the application to consume an excessive amount of memory. (CVE-2017-3253)

It was discovered that the Libraries component of OpenJDK did not validate the length of the object identifier read from the DER input before allocating memory to store the OID. An attacker able to make a Java application decode a specially crafted DER input could cause the application to consume an excessive amount of memory. (CVE-2016-5547)

It was discovered that the JAAS component of OpenJDK did not use the correct way to extract user DN from the result of the user search LDAP query. A specially crafted user LDAP entry could cause the application to use an incorrect DN. (CVE-2017-3252)

It was discovered that the Networking component of OpenJDK failed to properly parse user info from the URL. A remote attacker could cause a Java application to incorrectly parse an attacker supplied URL and interpret it differently from other applications processing the same URL. (CVE-2016-5552)

Multiple flaws were found in the Networking components in OpenJDK. An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. (CVE-2017-3261 , CVE-2017-3231)

A flaw was found in the way the DES/3DES cipher was used as part of the TLS/SSL protocol. A man-in-the-middle attacker could use this flaw to recover some plaintext data by capturing large amounts of encrypted traffic between TLS/SSL server and client if the communication used a DES/3DES based ciphersuite. (CVE-2016-2183) This update mitigates the CVE-2016-2183 issue by adding 3DES cipher suites to the list of legacy algorithms (defined using the jdk.tls.legacyAlgorithms security property) so they are only used if connecting TLS/SSL client and server do not share any other non-legacy cipher suite.

An update for java-1.8.0-ibm is now available for Red Hat Enterprise Linux 6 Supplementary and Red Hat Enterprise Linux 7 Supplementary.

Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

IBM Java SE version 8 includes the IBM Java Runtime Environment and the IBM Java Software Development Kit.

This update upgrades IBM Java SE 8 to version 8 SR4.

Security Fix(es) :

* This update fixes multiple vulnerabilities in the IBM Java Runtime Environment and the IBM Java Software Development Kit. Further information about these flaws can be found on the IBM Java Security alerts page, listed in the References section. (CVE-2016-5546, CVE-2016-5547, CVE-2016-5548, CVE-2016-5549, CVE-2016-5552, CVE-2017-3231, CVE-2017-3241, CVE-2017-3252, CVE-2017-3253, CVE-2017-3259, CVE-2017-3261, CVE-2017-3272, CVE-2017-3289)

An update for java-1.7.0-openjdk is now available for Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, and Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

The java-1.7.0-openjdk packages provide the OpenJDK 7 Java Runtime Environment and the OpenJDK 7 Java Software Development Kit.

Security Fix(es) :

* It was discovered that the RMI registry and DCG implementations in the RMI component of OpenJDK performed deserialization of untrusted inputs. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application. (CVE-2017-3241)

This issue was addressed by introducing whitelists of classes that can be deserialized by RMI registry or DCG. These whitelists can be customized using the newly introduced sun.rmi.registry.registryFilter and sun.rmi.transport.dgcFilter security properties.

* Multiple flaws were discovered in the Libraries and Hotspot components in OpenJDK. An untrusted Java application or applet could use these flaws to completely bypass Java sandbox restrictions.
(CVE-2017-3272, CVE-2017-3289)

* A covert timing channel flaw was found in the DSA implementation in the Libraries component of OpenJDK. A remote attacker could possibly use this flaw to extract certain information about the used key via a timing side channel. (CVE-2016-5548)

* It was discovered that the Libraries component of OpenJDK accepted ECSDA signatures using non-canonical DER encoding. This could cause a Java application to accept signature in an incorrect format not accepted by other cryptographic tools. (CVE-2016-5546)

* It was discovered that the 2D component of OpenJDK performed parsing of iTXt and zTXt PNG image chunks even when configured to ignore metadata. An attacker able to make a Java application parse a specially crafted PNG image could cause the application to consume an excessive amount of memory. (CVE-2017-3253)

* It was discovered that the Libraries component of OpenJDK did not validate the length of the object identifier read from the DER input before allocating memory to store the OID. An attacker able to make a Java application decode a specially crafted DER input could cause the application to consume an excessive amount of memory. (CVE-2016-5547)

* It was discovered that the JAAS component of OpenJDK did not use the correct way to extract user DN from the result of the user search LDAP query. A specially crafted user LDAP entry could cause the application to use an incorrect DN. (CVE-2017-3252)

* It was discovered that the Networking component of OpenJDK failed to properly parse user info from the URL. A remote attacker could cause a Java application to incorrectly parse an attacker supplied URL and interpret it differently from other applications processing the same URL. (CVE-2016-5552)

* Multiple flaws were found in the Networking components in OpenJDK.
An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions. (CVE-2017-3261, CVE-2017-3231)

* A flaw was found in the way the DES/3DES cipher was used as part of the TLS/SSL protocol. A man-in-the-middle attacker could use this flaw to recover some plaintext data by capturing large amounts of encrypted traffic between TLS/SSL server and client if the communication used a DES/3DES based ciphersuite. (CVE-2016-2183)

This update mitigates the CVE-2016-2183 issue by adding 3DES cipher suites to the list of legacy algorithms (defined using the jdk.tls.legacyAlgorithms security property) so they are only used if connecting TLS/SSL client and server do not share any other non-legacy cipher suite.

This update for java-1_8_0-ibm to version 8.0-4.0 fixes a lot of security issues (bsc#1024218): Following CVEs are fixed: CVE-2016-5552 CVE-2017-3231 CVE-2017-3241 CVE-2017-3253 CVE-2017-3259 CVE-2017-3261 CVE-2017-3272 CVE-2017-3289 CVE-2016-2183 CVE-2016-5547 CVE-2016-5548 CVE-2016-5549 CVE-2017-3252 More information can be found on:
https://developer.ibm.com/javasdk/support/security-vulnerabilities/

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for java-1_7_0-openjdk fixes the following issues :

  - Oracle Critical Patch Update of January 2017 to OpenJDK     7u131 (bsc#1020905) :

  - Security Fixes

  - S8138725: Add options for Javadoc generation

  - S8140353: Improve signature checking

  - S8151934, CVE-2017-3231: Resolve class resolution

  - S8156804, CVE-2017-3241: Better constraint checking

  - S8158406: Limited Parameter Processing

  - S8158997: JNDI Protocols Switch

  - S8159507: RuntimeVisibleAnnotation validation

  - S8161218: Better bytecode loading

  - S8161743, CVE-2017-3252: Provide proper login context

  - S8162577: Standardize logging levels

  - S8162973: Better component components

  - S8164143, CVE-2017-3260: Improve components for menu     items

  - S8164147, CVE-2017-3261: Improve streaming socket output

  - S8165071, CVE-2016-2183: Expand TLS support

  - S8165344, CVE-2017-3272: Update concurrency support

  - S8166988, CVE-2017-3253: Improve image processing     performance

  - S8167104, CVE-2017-3289: Additional class construction     refinements

  - S8167223, CVE-2016-5552: URL handling improvements

  - S8168705, CVE-2016-5547: Better ObjectIdentifier     validation

  - S8168714, CVE-2016-5546: Tighten ECDSA validation

  - S8168728, CVE-2016-5548: DSA signing improvments

  - S8168724, CVE-2016-5549: ECDSA signing improvments

  - S6253144: Long narrowing conversion should describe the     algorithm used and implied 'risks'

  - S6328537: Improve javadocs for Socket class by adding     references to SocketOptions

  - S6978886: javadoc shows stacktrace after print error     resulting from disk full

  - S6995421: Eliminate the static dependency to     sun.security.ec.ECKeyFactory

  - S6996372: synchronizing handshaking hash

  - S7027045: (doc) java/awt/Window.java has several typos     in javadoc

  - S7054969: Null-check-in-finally pattern in java/security     documentation

  - S7072353: JNDI libraries do not build with javac
    -Xlint:all -Werror

  - S7075563: Broken link in 'javax.swing.SwingWorker'

  - S7077672: jdk8_tl nightly fail in step-2 build on     8/10/11

  - S7088502: Security libraries don't build with javac
    -Werror

  - S7092447: Clarify the default locale used in each locale     sensitive operation

  - S7093640: Enable client-side TLS 1.2 by default

  - S7103570: AtomicIntegerFieldUpdater does not work when     SecurityManager is installed

  - S7117360: Warnings in java.util.concurrent.atomic     package

  - S7117465: Warning cleanup for IMF classes

  - S7187144: JavaDoc for ScriptEngineFactory.getProgram()     contains an error

  - S8000418: javadoc should used a standard 'generated by     javadoc' string

  - S8000666: javadoc should write directly to Writer     instead of composing strings

  - S8000673: remove dead code from HtmlWriter and subtypes

  - S8000970: break out auxiliary classes that will prevent     multi-core compilation of the JDK

  - S8001669: javadoc internal DocletAbortException should     set cause when appropriate

  - S8008949: javadoc stopped copying doc-files

  - S8011402: Move blacklisting certificate logic from hard     code to data

  - S8011547: Update XML Signature implementation to Apache     Santuario 1.5.4

  - S8012288: XML DSig API allows wrong tag names and extra     elements in SignedInfo

  - S8016217: More javadoc warnings

  - S8017325: Cleanup of the javadoc <code> tag in     java.security.cert

  - S8017326: Cleanup of the javadoc <code> tag in     java.security.spec

  - S8019772: Fix doclint issues in javax.crypto and     javax.security subpackages

  - S8020557: javadoc cleanup in javax.security

  - S8020688: Broken links in documentation at     http://docs.oracle.com/javase/6/docs/api/index.

  - S8021108: Clean up doclint warnings and errors in     java.text package

  - S8021417: Fix doclint issues in java.util.concurrent

  - S8021833: javadoc cleanup in java.net

  - S8022120: JCK test     api/javax_xml/crypto/dsig/TransformService/index_ParamMe     thods fails

  - S8022175: Fix doclint warnings in javax.print

  - S8022406: Fix doclint issues in java.beans

  - S8022746: List of spelling errors in API doc

  - S8024779: [macosx] SwingNode crashes on exit

  - S8025085: [javadoc] some errors in javax/swing

  - S8025218: [javadoc] some errors in java/awt classes

  - S8025249: [javadoc] fix some javadoc errors in     javax/swing/

  - S8025409: Fix javadoc comments errors and warning     reported by doclint report

  - S8026021: more fix of javadoc errors and warnings     reported by doclint, see the description

  - S8037099: [macosx] Remove all references to GC from     native OBJ-C code

  - S8038184: XMLSignature throws     StringIndexOutOfBoundsException if ID attribute value is     empty String

  - S8038349: Signing XML with DSA throws Exception when key     is larger than 1024 bits

  - S8049244: XML Signature performance issue caused by     unbuffered signature data

  - S8049432: New tests for TLS property     jdk.tls.client.protocols

  - S8050893: (smartcardio) Invert reset argument in tests     in sun/security/smartcardio

  - S8059212: Modify regression tests so that they do not     just fail if no cardreader found

  - S8068279: (typo in the spec)     javax.script.ScriptEngineFactory.getLanguageName

  - S8068491: Update the protocol for references of     docs.oracle.com to HTTPS.

  - S8069038: javax/net/ssl/TLS/TLSClientPropertyTest.java     needs to be updated for JDK-8061210

  - S8076369: Introduce the jdk.tls.client.protocols system     property for JDK 7u

  - S8139565: Restrict certificates with DSA keys less than     1024 bits

  - S8140422: Add mechanism to allow non default root CAs to     be not subject to algorithm restrictions

  - S8140587: Atomic*FieldUpdaters should use     Class.isInstance instead of direct class check

  - S8143959: Certificates requiring blacklisting

  - S8145984: [macosx] sun.lwawt.macosx.CAccessible leaks

  - S8148516: Improve the default strength of EC in JDK

  - S8149029: Secure validation of XML based digital     signature always enabled when checking wrapping attacks

  - S8151893: Add security property to configure XML     Signature secure validation mode

  - S8155760: Implement Serialization Filtering

  - S8156802: Better constraint checking

  - S8161228: URL objects with custom protocol handlers have     port changed after deserializing

  - S8161571: Verifying ECDSA signatures permits trailing     bytes

  - S8163304: jarsigner -verbose -verify should print the     algorithms used to sign the jar

  - S8164908: ReflectionFactory support for IIOP and custom     serialization

  - S8165230: RMIConnection addNotificationListeners failing     with specific inputs

  - S8166393: disabledAlgorithms property should not be     strictly parsed

  - S8166591: [macos 10.12] Trackpad scrolling of text on OS     X 10.12 Sierra is very fast (Trackpad, Retina only)

  - S8166739: Improve extensibility of ObjectInputFilter     information passed to the filter

  - S8166875: (tz) Support tzdata2016g

  - S8166878: Connection reset during TLS handshake

  - S8167356: Follow up fix for jdk8 backport of 8164143.
    Changes for CMenuComponent.m were missed

  - S8167459: Add debug output for indicating if a chosen     ciphersuite was legacy

  - S8167472: Chrome interop regression with JDK-8148516

  - S8167591: Add MD5 to signed JAR restrictions

  - S8168861: AnchorCertificates uses hardcoded password for     cacerts keystore

  - S8168993: JDK8u121 L10n resource file update

  - S8169191: (tz) Support tzdata2016i

  - S8169688: Backout (remove) MD5 from     jdk.jar.disabledAlgorithms for January CPU

  - S8169911: Enhanced tests for jarsigner -verbose -verify     after JDK-8163304

  - S8170131: Certificates not being blocked by     jdk.tls.disabledAlgorithms property

  - S8170268: 8u121 L10n resource file update - msgdrop 20

  - S8173622: Backport of 7180907 is incomplete

  - S8173849: Fix use of java.util.Base64 in test cases

  - S8173854: [TEST] Update DHEKeySizing test case following     8076328 & 8081760

  - CVE-2017-3259 Vulnerability allows unauthenticated     attacker with network access via multiple protocols to     compromise Java SE.

  - Backports

  - S7102489, PR3316, RH1390708: RFE: cleanup jlong typedef     on __APPLE__and _LLP64 systems.

  - S8000351, PR3316, RH1390708: Tenuring threshold should     be unsigned

  - S8153711, PR3315, RH1284948: [REDO] GlobalRefs never     deleted when processing invokeMethod command

  - S8170888, PR3316, RH1390708: [linux] support for cgroup     memory limits in container (ie Docker) environments

  - Bug fixes

  - PR3318: Replace 'infinality' with 'improved font     rendering' (--enable-improved-font-rendering)

  - PR3318: Fix compatibility with vanilla Fontconfig

  - PR3318: Fix glyph y advance

  - PR3318: Always round glyph advance in 26.6 space

  - PR3318: Simplify glyph advance handling

  - PR3324: Fix NSS_LIBDIR substitution in     make_generic_profile.sh broken by PR1989

  - AArch64 port

  - S8165673, PR3320: AArch64: Fix JNI floating point     argument handling

This update was imported from the SUSE:SLE-12:Update update project.

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2017:0336 advisory.

  - SSL/TLS: Birthday attack against 64-bit block ciphers (SWEET32) (CVE-2016-2183)

  - OpenJDK: incorrect ECDSA signature extraction from the DER input (Libraries, 8168714) (CVE-2016-5546)

  - OpenJDK: missing ObjectIdentifier length check (Libraries, 8168705) (CVE-2016-5547)

  - OpenJDK: DSA implementation timing attack (Libraries, 8168728) (CVE-2016-5548)

  - OpenJDK: ECDSA implementation timing attack (Libraries, 8168724) (CVE-2016-5549)

  - OpenJDK: incorrect URL parsing in URLStreamHandler (Networking, 8167223) (CVE-2016-5552)

  - OpenJDK: URLClassLoader insufficient access control checks (Networking, 8151934) (CVE-2017-3231)

  - OpenJDK: untrusted input deserialization in RMI registry and DCG (RMI, 8156802) (CVE-2017-3241)

  - OpenJDK: LdapLoginModule incorrect userDN extraction (JAAS, 8161743) (CVE-2017-3252)

  - OpenJDK: imageio PNGImageReader failed to honor ignoreMetadata for iTXt and zTXt chunks (2D, 8166988)     (CVE-2017-3253)

  - Oracle JDK: unspecified vulnerability fixed in 6u141, 7u131, and 8u121 (Deployment) (CVE-2017-3259)

  - OpenJDK: integer overflow in SocketOutputStream boundary check (Networking, 8164147) (CVE-2017-3261)

  - OpenJDK: insufficient protected field access checks in atomic field updaters (Libraries, 8165344)     (CVE-2017-3272)

  - OpenJDK: insecure class construction (Hotspot, 8167104) (CVE-2017-3289)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
96628	Oracle Java SE Multiple Vulnerabilities (January 2017 CPU) (SWEET32)	Nessus	Windows	2017/1/19	2024/12/20	critical
99861	EulerOS 2.0 SP1 : java-1.8.0-openjdk (EulerOS-SA-2017-1015)	Nessus	Huawei Local Security Checks	2017/5/1	2025/12/22	critical
96693	RHEL 6 / 7 : java-1.8.0-openjdk (RHSA-2017:0180)	Nessus	Red Hat Local Security Checks	2017/1/23	2026/1/5	critical
96757	Scientific Linux Security Update : java-1.8.0-openjdk on SL6.x, SL7.x i386/x86_64 (20170120)	Nessus	Scientific Linux Local Security Checks	2017/1/25	2026/1/2	critical
96809	Amazon Linux AMI : java-1.8.0-openjdk (ALAS-2017-791)	Nessus	Amazon Linux Local Security Checks	2017/1/27	2026/1/2	critical
97095	RHEL 6 / 7 : java-1.8.0-ibm (RHSA-2017:0263)	Nessus	Red Hat Local Security Checks	2017/2/10	2026/1/1	critical
97134	CentOS 5 / 6 / 7 : java-1.7.0-openjdk (CESA-2017:0269)	Nessus	CentOS Local Security Checks	2017/2/14	2026/1/1	critical
97187	SUSE SLES12 Security Update : java-1_8_0-ibm (SUSE-SU-2017:0460-1)	Nessus	SuSE Local Security Checks	2017/2/15	2026/1/1	critical
97287	openSUSE Security Update : java-1_7_0-openjdk (openSUSE-2017-278)	Nessus	SuSE Local Security Checks	2017/2/21	2025/12/31	critical
97460	RHEL 6 / 7 : java-1.7.1-ibm (RHSA-2017:0336)	Nessus	Red Hat Local Security Checks	2017/3/1	2024/4/24	critical

检测

插件搜索

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical