Several vulnerabilities have been discovered in OpenJDK, an implementation of the Oracle Java platform, resulting in denial of service, unauthorized access, sandbox bypass or HTTP header injection.

For Debian 7 'Wheezy', these problems have been fixed in version 7u171-2.6.13-1~deb7u1.

We recommend that you upgrade your openjdk-7 packages.

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

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

    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):

    * A flaw was found in the AWT component of OpenJDK. An untrusted Java application or applet could use this     flaw to bypass certain Java sandbox restrictions. (CVE-2018-2641)

    * It was discovered that the LDAPCertStore class in the JNDI component of OpenJDK failed to securely     handle LDAP referrals. An attacker could possibly use this flaw to make it fetch attacker controlled     certificate data. (CVE-2018-2633)

    * The JGSS component of OpenJDK ignores the value of the javax.security.auth.useSubjectCredsOnly property     when using HTTP/SPNEGO authentication and always uses global credentials. It was discovered that this     could cause global credentials to be unexpectedly used by an untrusted Java application. (CVE-2018-2634)

    * It was discovered that the JMX component of OpenJDK failed to properly set the deserialization filter     for the SingleEntryRegistry in certain cases. A remote attacker could possibly use this flaw to bypass     intended deserialization restrictions. (CVE-2018-2637)

    * It was discovered that the LDAP component of OpenJDK failed to properly encode special characters in     user names when adding them to an LDAP search query. A remote attacker could possibly use this flaw to     manipulate LDAP queries performed by the LdapLoginModule class. (CVE-2018-2588)

    * It was discovered that the DNS client implementation in the JNDI component of OpenJDK did not use random     source ports when sending out DNS queries. This could make it easier for a remote attacker to spoof     responses to those queries. (CVE-2018-2599)

    * It was discovered that the I18n component of OpenJDK could use an untrusted search path when loading     resource bundle classes. A local attacker could possibly use this flaw to execute arbitrary code as     another local user by making their Java application load an attacker controlled class file.
    (CVE-2018-2602)

    * It was discovered that the Libraries component of OpenJDK failed to sufficiently limit the amount of     memory allocated when reading DER encoded input. A remote attacker could possibly use this flaw to make a     Java application use an excessive amount of memory if it parsed attacker supplied DER encoded input.
    (CVE-2018-2603)

    * It was discovered that the key agreement implementations in the JCE component of OpenJDK did not     guarantee sufficient strength of used keys to adequately protect generated shared secret. This could make     it easier to break data encryption by attacking key agreement rather than the encryption using the     negotiated secret. (CVE-2018-2618)

    * It was discovered that the JGSS component of OpenJDK failed to properly handle GSS context in the native     GSS library wrapper in certain cases. A remote attacker could possibly make a Java application using JGSS     to use a previously freed context. (CVE-2018-2629)

    * It was discovered that multiple classes in the Libraries, AWT, and JNDI components of OpenJDK did not     sufficiently validate input when creating object instances from the serialized form. A specially-crafted     input could cause a Java application to create objects with an inconsistent state or use an excessive     amount of memory when deserialized. (CVE-2018-2663, CVE-2018-2677, CVE-2018-2678)

    * It was discovered that multiple encryption key classes in the Libraries component of OpenJDK did not     properly synchronize access to their internal data. This could possibly cause a multi-threaded Java     application to apply weak encryption to data because of the use of a key that was zeroed out.
    (CVE-2018-2579)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

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 :

  - Multiple flaws were found in the Hotspot and AWT     components of OpenJDK. An untrusted Java application or     applet could use these flaws to bypass certain Java     sandbox restrictions. (CVE-2018-2582, CVE-2018-2641)

  - It was discovered that the LDAPCertStore class in the     JNDI component of OpenJDK failed to securely handle     LDAP referrals. An attacker could possibly use this     flaw to make it fetch attacker controlled certificate     data. (CVE-2018-2633)

  - The JGSS component of OpenJDK ignores the value of the     javax.security.auth.useSubjectCredsOnly property when     using HTTP/SPNEGO authentication and always uses global     credentials. It was discovered that this could cause     global credentials to be unexpectedly used by an     untrusted Java application. (CVE-2018-2634)

  - It was discovered that the JMX component of OpenJDK     failed to properly set the deserialization filter for     the SingleEntryRegistry in certain cases. A remote     attacker could possibly use this flaw to bypass     intended deserialization restrictions. (CVE-2018-2637)

  - It was discovered that the LDAP component of OpenJDK     failed to properly encode special characters in user     names when adding them to an LDAP search query. A     remote attacker could possibly use this flaw to     manipulate LDAP queries performed by the     LdapLoginModule class. (CVE-2018-2588)

  - It was discovered that the DNS client implementation in     the JNDI component of OpenJDK did not use random source     ports when sending out DNS queries. This could make it     easier for a remote attacker to spoof responses to     those queries. (CVE-2018-2599)

  - It was discovered that the I18n component of OpenJDK     could use an untrusted search path when loading     resource bundle classes. A local attacker could     possibly use this flaw to execute arbitrary code as     another local user by making their Java application     load an attacker controlled class file. (CVE-2018-2602)

  - It was discovered that the Libraries component of     OpenJDK failed to sufficiently limit the amount of     memory allocated when reading DER encoded input. A     remote attacker could possibly use this flaw to make a     Java application use an excessive amount of memory if     it parsed attacker supplied DER encoded input.
    (CVE-2018-2603)

  - It was discovered that the key agreement     implementations in the JCE component of OpenJDK did not     guarantee sufficient strength of used keys to     adequately protect generated shared secret. This could     make it easier to break data encryption by attacking     key agreement rather than the encryption using the     negotiated secret. (CVE-2018-2618)

  - It was discovered that the JGSS component of OpenJDK     failed to properly handle GSS context in the native GSS     library wrapper in certain cases. A remote attacker     could possibly make a Java application using JGSS to     use a previously freed context. (CVE-2018-2629)

  - It was discovered that multiple classes in the     Libraries, AWT, and JNDI components of OpenJDK did not     sufficiently validate input when creating object     instances from the serialized form. A specially-crafted     input could cause a Java application to create objects     with an inconsistent state or use an excessive amount     of memory when deserialized. (CVE-2018-2663,     CVE-2018-2677, CVE-2018-2678)

  - It was discovered that multiple encryption key classes     in the Libraries component of OpenJDK did not properly     synchronize access to their internal data. This could     possibly cause a multi-threaded Java application to     apply weak encryption to data because of the use of a     key that was zeroed out. (CVE-2018-2579)

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.

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

    Oracle Java SE version 7 includes the Oracle Java Runtime Environment and the Oracle Java Software     Development Kit.

    This update upgrades Oracle Java SE 7 to version 7 Update 171.

    Security Fix(es):

    * This update fixes multiple vulnerabilities in the Oracle Java Runtime Environment and the Oracle Java     Software Development Kit. Further information about these flaws can be found on the Oracle Java SE     Critical Patch Update Advisory page listed in the References section. (CVE-2018-2579, CVE-2018-2581,     CVE-2018-2588, CVE-2018-2599, CVE-2018-2602, CVE-2018-2603, CVE-2018-2618, CVE-2018-2629, CVE-2018-2633,     CVE-2018-2634, CVE-2018-2637, CVE-2018-2641, CVE-2018-2657, CVE-2018-2663, CVE-2018-2677, CVE-2018-2678)

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

The version of Oracle (formerly Sun) Java SE or Java for Business installed on the remote host is prior to 9 Update 4, 8 Update 161, 7 Update 171, or 6 Update 1888888881. It is, therefore, affected by multiple vulnerabilities related to the following components :

  - AWT
  - Deployment
  - Hotspot
  - I18n
  - Installer
  - JCE
  - JGSS
  - JMX
  - JNDI
  - JavaFX
  - LDAP
  - Libraries
  - Serialization

The version of Oracle (formerly Sun) Java SE or Java for Business installed on the remote host is prior to 9 Update 4, 8 Update 161, 7 Update 171, or 6 Update 181. It is, therefore, affected by multiple vulnerabilities related to the following components :

 - AWT
 - Deployment
 - Hotspot
 - I18n
 - Installer
 - JCE
 - JGSS
 - JMX
 - JNDI
 - JavaFX
 - LDAP
 - Libraries
 - Serialization

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
108815	Debian DLA-1339-1 : openjdk-7 security update	Nessus	Debian Local Security Checks	2018/4/4	2024/11/21	high
107016	RHEL 6 / 7 : java-1.7.0-openjdk (RHSA-2018:0349)	Nessus	Red Hat Local Security Checks	2018/2/27	2025/10/27	high
106403	EulerOS 2.0 SP2 : java-1.8.0-openjdk (EulerOS-SA-2018-1028)	Nessus	Huawei Local Security Checks	2018/1/29	2025/10/31	high
106183	RHEL 7 : java-1.7.0-oracle (RHSA-2018:0100)	Nessus	Red Hat Local Security Checks	2018/1/19	2025/3/20	high
106191	Oracle Java SE Multiple Vulnerabilities (January 2018 CPU) (Unix)	Nessus	Misc.	2018/1/19	2024/6/20	high
700656	Oracle Java SE 6 < Update 181 / 7 < Update 171 / 8 < Update 161 / 9 < Update 4 Multiple Vulnerabilities (January 2018 CPU)	Nessus Network Monitor	Web Clients	2019/5/2	2019/5/2	high

检测

插件搜索

high

high

high

high

high

high