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

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 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.

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

Security issues fixed in OpenJDK 7u171 (January 2018 CPU)(bsc#1076366) :

  - CVE-2018-2579: Improve key keying case

  - CVE-2018-2588: Improve LDAP logins

  - CVE-2018-2599: Improve reliability of DNS lookups

  - CVE-2018-2602: Improve usage messages

  - CVE-2018-2603: Improve PKCS usage

  - CVE-2018-2618: Stricter key generation

  - CVE-2018-2629: Improve GSS handling

  - CVE-2018-2633: Improve LDAP lookup robustness

  - CVE-2018-2634: Improve property negotiations

  - CVE-2018-2637: Improve JMX supportive features

  - CVE-2018-2641: Improve GTK initialization

  - CVE-2018-2663: More refactoring for deserialization     cases

  - CVE-2018-2677: More refactoring for client     deserialization cases

  - CVE-2018-2678: More refactoring for naming

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

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

    IBM Java SE version 7 Release 1 includes the IBM Java Runtime Environment and the IBM Java Software     Development Kit.

    This update upgrades IBM Java SE 7 to version 7R1 SR4-FP20.

    Security Fix(es):

    * OpenJDK: insufficient validation of the invokeinterface instruction (Hotspot, 8174962) (CVE-2018-2582)

    * OpenJDK: LDAPCertStore insecure handling of LDAP referrals (JNDI, 8186606) (CVE-2018-2633)

    * OpenJDK: use of global credentials for HTTP/SPNEGO (JGSS, 8186600) (CVE-2018-2634)

    * OpenJDK: SingleEntryRegistry incorrect setup of deserialization filter (JMX, 8186998) (CVE-2018-2637)

    * OpenJDK: GTK library loading use-after-free (AWT, 8185325) (CVE-2018-2641)

    * OpenJDK: LdapLoginModule insufficient username encoding in LDAP query (LDAP, 8178449) (CVE-2018-2588)

    * OpenJDK: DnsClient missing source port randomization (JNDI, 8182125) (CVE-2018-2599)

    * OpenJDK: loading of classes from untrusted locations (I18n, 8182601) (CVE-2018-2602)

    * OpenJDK: DerValue unbounded memory allocation (Libraries, 8182387) (CVE-2018-2603)

    * OpenJDK: insufficient strength of key agreement (JCE, 8185292) (CVE-2018-2618)

    * Oracle JDK: unspecified vulnerability fixed in 6u181 and 7u171 (Serialization) (CVE-2018-2657)

    * OpenJDK: ArrayBlockingQueue deserialization to an inconsistent state (Libraries, 8189284)     (CVE-2018-2663)

    * OpenJDK: unbounded memory allocation during deserialization (AWT, 8190289) (CVE-2018-2677)

    * OpenJDK: unbounded memory allocation in BasicAttributes deserialization (JNDI, 8191142) (CVE-2018-2678)

    * OpenJDK: unsynchronized access to encryption key data (Libraries, 8172525) (CVE-2018-2579)

    For more details about the security issue(s), including the impact, a CVSS score, and other related     information, refer to the CVE page(s) listed in the References section.

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.7.0-openjdk packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

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

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.

DerValue unbounded memory allocation :

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)

Unsynchronized access to encryption key data

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)

Use of global credentials for HTTP/SPNEGO

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)

Loading of classes from untrusted locations :

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)

GTK library loading use-after-free :

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: AWT). Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, Java SE Embedded, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE, Java SE Embedded accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). (CVE-2018-2641)

LdapLoginModule insufficient username encoding in LDAP query :

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)

SingleEntryRegistry incorrect setup of deserialization filter :

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)

Insufficient strength of key agreement :

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)

GSS context use-after-free :

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)

LDAPCertStore insecure handling of LDAP referrals :

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)

DnsClient missing source port randomization :

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)

Unbounded memory allocation in BasicAttributes deserialization :

Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: JNDI). Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded, JRockit. Note: This vulnerability applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It 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.
(CVE-2018-2678)

ArrayBlockingQueue deserialization to an inconsistent state :

Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: Libraries). Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit.
Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded, JRockit. Note: This vulnerability applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. It 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.
(CVE-2018-2663)

Unbounded memory allocation during deserialization :

Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: AWT). Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Java SE, Java SE Embedded.
Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). (CVE-2018-2677)

The remote Ubuntu 16.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-3613-1 advisory.

    It was discovered that a race condition existed in the cryptography implementation in OpenJDK. An attacker     could possibly use this to expose sensitive information. (CVE-2018-2579)

    It was discovered that the Hotspot component of OpenJDK did not properly validate uses of the     invokeinterface JVM instruction. An attacker could possibly use this to access unauthorized resources.
    (CVE-2018-2582)

    It was discovered that the LDAP implementation in OpenJDK did not properly encode login names. A remote     attacker could possibly use this to expose sensitive information. (CVE-2018-2588)

    It was discovered that the DNS client implementation in OpenJDK did not properly randomize source ports. A     remote attacker could use this to spoof responses to DNS queries made by Java applications.
    (CVE-2018-2599)

    It was discovered that the Internationalization component of OpenJDK did not restrict search paths when     loading resource bundle classes. A local attacker could use this to trick a user into running malicious     code. (CVE-2018-2602)

    It was discovered that OpenJDK did not properly restrict memory allocations when parsing DER input. A     remote attacker could possibly use this to cause a denial of service. (CVE-2018-2603)

    It was discovered that the Java Cryptography Extension (JCE) implementation in OpenJDK in some situations     did not guarantee sufficient strength of keys during key agreement. An attacker could use this to expose     sensitive information. (CVE-2018-2618)

    It was discovered that the Java GSS implementation in OpenJDK in some situations did not properly handle     GSS contexts in the native GSS library. An attacker could possibly use this to access unauthorized     resources. (CVE-2018-2629)

    It was discovered that the LDAP implementation in OpenJDK did not properly handle LDAP referrals in some     situations. An attacker could possibly use this to expose sensitive information or gain unauthorized     privileges. (CVE-2018-2633)

    It was discovered that the Java GSS implementation in OpenJDK in some situations did not properly apply     subject credentials. An attacker could possibly use this to expose sensitive information or gain access to     unauthorized resources. (CVE-2018-2634)

    It was discovered that the Java Management Extensions (JMX) component of OpenJDK did not properly apply     deserialization filters in some situations. An attacker could use this to bypass deserialization     restrictions. (CVE-2018-2637)

    It was discovered that a use-after-free vulnerability existed in the AWT component of OpenJDK when loading     the GTK library. An attacker could possibly use this to execute arbitrary code and escape Java sandbox     restrictions. (CVE-2018-2641)

    It was discovered that in some situations OpenJDK did not properly validate objects when performing     deserialization. An attacker could use this to cause a denial of service (application crash or excessive     memory consumption). (CVE-2018-2663)

    It was discovered that the AWT component of OpenJDK did not properly restrict the amount of memory     allocated when deserializing some objects. An attacker could use this to cause a denial of service     (excessive memory consumption). (CVE-2018-2677)

    It was discovered that the JNDI component of OpenJDK did not properly restrict the amount of memory     allocated when deserializing objects in some situations. An attacker could use this to cause a denial of     service (excessive memory consumption). (CVE-2018-2678)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: JNDI).
    Supported versions that are affected are Java SE: 6u171, 7u161, 8u152 and 9.0.1; Java SE Embedded: 8u151;
    JRockit: R28.3.16. Difficult to exploit vulnerability allows unauthenticated attacker with network access     via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. Successful attacks require human     interaction from a person other than the attacker and while the vulnerability is in Java SE, Java SE     Embedded, JRockit, attacks may significantly impact additional products. Successful attacks of this     vulnerability can result in takeover of Java SE, Java SE Embedded, JRockit. Note: This vulnerability     applies to client and server deployment of Java. This vulnerability can be exploited through sandboxed     Java Web Start applications and sandboxed Java applets. It 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. (CVE-2018-2633)

Note that Nessus relies on the presence of the package as reported by the vendor.

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	名称	产品	系列	发布时间	最近更新时间	严重程度
106191	Oracle Java SE Multiple Vulnerabilities (January 2018 CPU) (Unix)	Nessus	Misc.	2018/1/19	2024/6/20	high
106403	EulerOS 2.0 SP2 : java-1.8.0-openjdk (EulerOS-SA-2018-1028)	Nessus	Huawei Local Security Checks	2018/1/29	2021/1/6	medium
107016	RHEL 6 / 7 : java-1.7.0-openjdk (RHSA-2018:0349)	Nessus	Red Hat Local Security Checks	2018/2/27	2025/3/24	high
108357	openSUSE Security Update : java-1_7_0-openjdk (openSUSE-2018-256)	Nessus	SuSE Local Security Checks	2018/3/15	2025/1/30	high
108362	RHEL 6 : java-1.7.1-ibm (RHSA-2018:0521)	Nessus	Red Hat Local Security Checks	2018/3/15	2025/3/24	high
108463	EulerOS 2.0 SP2 : java-1.7.0-openjdk (EulerOS-SA-2018-1059)	Nessus	Huawei Local Security Checks	2018/3/20	2025/1/28	high
108599	Amazon Linux AMI : java-1.7.0-openjdk (ALAS-2018-974)	Nessus	Amazon Linux Local Security Checks	2018/3/27	2024/12/6	high
108793	Ubuntu 16.04 LTS : OpenJDK 8 vulnerabilities (USN-3613-1)	Nessus	Ubuntu Local Security Checks	2018/4/3	2024/8/27	high
108815	Debian DLA-1339-1 : openjdk-7 security update	Nessus	Debian Local Security Checks	2018/4/4	2024/11/21	high
221864	Linux Distros Unpatched Vulnerability : CVE-2018-2633	Nessus	Misc.	2025/3/4	2025/9/1	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

medium

high

high

high

high

high

high

high

high

high