Ubuntu 3613-1: OpenJDK 8 vulnerabilities

    Date02 Apr 2018
    CategoryUbuntu
    3089
    Posted ByAnthony Pell
    Several security issues were fixed in OpenJDK 8.
    ==========================================================================
    Ubuntu Security Notice USN-3613-1
    April 02, 2018
    
    openjdk-8 vulnerabilities
    ==========================================================================
    
    A security issue affects these releases of Ubuntu and its derivatives:
    
    - Ubuntu 17.10
    - Ubuntu 16.04 LTS
    
    Summary:
    
    Several security issues were fixed in OpenJDK 8.
    
    Software Description:
    - openjdk-8: Open Source Java implementation
    
    Details:
    
    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 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)
    
    Update instructions:
    
    The problem can be corrected by updating your system to the following
    package versions:
    
    Ubuntu 17.10:
      openjdk-8-jdk                   8u162-b12-0ubuntu0.17.10.2
      openjdk-8-jdk-headless          8u162-b12-0ubuntu0.17.10.2
      openjdk-8-jre                   8u162-b12-0ubuntu0.17.10.2
      openjdk-8-jre-headless          8u162-b12-0ubuntu0.17.10.2
      openjdk-8-jre-zero              8u162-b12-0ubuntu0.17.10.2
    
    Ubuntu 16.04 LTS:
      openjdk-8-jdk                   8u162-b12-0ubuntu0.16.04.2
      openjdk-8-jdk-headless          8u162-b12-0ubuntu0.16.04.2
      openjdk-8-jre                   8u162-b12-0ubuntu0.16.04.2
      openjdk-8-jre-headless          8u162-b12-0ubuntu0.16.04.2
      openjdk-8-jre-jamvm             8u162-b12-0ubuntu0.16.04.2
      openjdk-8-jre-zero              8u162-b12-0ubuntu0.16.04.2
    
    This update uses a new upstream release, which includes additional bug
    fixes. After a standard system update you need to restart any Java
    applications or applets to make all the necessary changes.
    
    References:
      https://usn.ubuntu.com/usn/usn-3613-1
      CVE-2018-2579, CVE-2018-2582, 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-2663, CVE-2018-2677, CVE-2018-2678
    
    Package Information:
      https://launchpad.net/ubuntu/+source/openjdk-8/8u162-b12-0ubuntu0.17.10.2
      https://launchpad.net/ubuntu/+source/openjdk-8/8u162-b12-0ubuntu0.16.04.2
    
    You are not authorised to post comments.

    Comments powered by CComment

    LinuxSecurity Poll

    What do you think of the articles on LinuxSecurity?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    /main-polls/24-what-do-you-think-of-the-quality-of-the-articles-on-linuxsecurity?task=poll.vote&format=json
    24
    radio
    [{"id":"87","title":"Excellent, don't change a thing!","votes":"36","type":"x","order":"1","pct":50.7,"resources":[]},{"id":"88","title":"Should be more technical","votes":"10","type":"x","order":"2","pct":14.08,"resources":[]},{"id":"89","title":"Should include more HOWTOs","votes":"25","type":"x","order":"3","pct":35.21,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.