This update for java-1_8_0-ibm to 8.0.5.20 fixes the following security issues :

CVE-2018-2952: Vulnerability in subcomponent: Concurrency. Difficult to exploit vulnerability allowed unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded, JRockit. 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 (bsc#1104668)

CVE-2018-2940: Vulnerability in subcomponent: Libraries. Easily exploitable vulnerability allowed 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 read access to a subset of Java SE, Java SE Embedded accessible data (bsc#1104668)

CVE-2018-2973: Vulnerability in subcomponent: JSSE. Difficult to exploit vulnerability allowed unauthenticated attacker with network access via SSL/TLS to compromise Java SE, Java SE Embedded. 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 (bsc#1104668)

CVE-2018-2964: Vulnerability in subcomponent: Deployment. Difficult to exploit vulnerability allowed unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Java SE. (bsc#1104668)

CVE-2016-0705: Prevent double free in the dsa_priv_decode function that allowed remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a malformed DSA private key (bsc#1104668)

CVE-2017-3732: Prevent carry propagating bug in the x86_64 Montgomery squaring procedure (bsc#1104668)

CVE-2017-3736: Prevent carry propagating bug in the x86_64 Montgomery squaring procedure (bsc#1104668)

CVE-2018-1517: Unspecified vulnerability (bsc#1104668)

CVE-2018-1656: Unspecified vulnerability (bsc#1104668)

CVE-2018-12539: Users other than the process owner might have been able to use Java Attach API to connect to an IBM JVM on the same machine and use Attach API operations, which includes the ability to execute untrusted native code (bsc#1104668)

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 openssl fixes the following issues :

  - OpenSSL Security Advisory [07 Dec 2017]

  - CVE-2017-3737: OpenSSL 1.0.2 (starting from version     1.0.2b) introduced an \'error state\' mechanism. The     intent was that if a fatal error occurred during a     handshake then OpenSSL would move into the error state     and would immediately fail if you attempted to continue     the handshake. This works as designed for the explicit     handshake functions (SSL_do_handshake(), SSL_accept()     and SSL_connect()), however due to a bug it does not     work correctly if SSL_read() or SSL_write() is called     directly. In that scenario, if the handshake fails then     a fatal error will be returned in the initial function     call. If SSL_read()/SSL_write() is subsequently called     by the application for the same SSL object then it will     succeed and the data is passed without being     decrypted/encrypted directly from the SSL/TLS record     layer. In order to exploit this issue an application bug     would have to be present that resulted in a call to     SSL_read()/SSL_write() being issued after having already     received a fatal error. OpenSSL version 1.0.2b-1.0.2m     are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is     not affected. (bsc#1071905)

  - CVE-2017-3738: There is an overflow bug in the AVX2     Montgomery multiplication procedure used in     exponentiation with 1024-bit moduli. No EC algorithms     are affected. Analysis suggests that attacks against RSA     and DSA as a result of this defect would be very     difficult to perform and are not believed likely.
    Attacks against DH1024 are considered just feasible,     because most of the work necessary to deduce information     about a private key may be performed offline. The amount     of resources required for such an attack would be     significant. However, for an attack on TLS to be     meaningful, the server would have to share the DH1024     private key among multiple clients, which is no longer     an option since CVE-2016-0701. This only affects     processors that support the AVX2 but not ADX extensions     like Intel Haswell (4th generation). Note: The impact     from this issue is similar to CVE-2017-3736,     CVE-2017-3732 and CVE-2015-3193. (bsc#1071906)

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

This update for openssl fixes the following issues :

  - OpenSSL Security Advisory [07 Dec 2017]

  - CVE-2017-3737: OpenSSL 1.0.2 (starting from version     1.0.2b) introduced an \'error state\' mechanism. The     intent was that if a fatal error occurred during a     handshake then OpenSSL would move into the error state     and would immediately fail if you attempted to continue     the handshake. This works as designed for the explicit     handshake functions (SSL_do_handshake(), SSL_accept()     and SSL_connect()), however due to a bug it does not     work correctly if SSL_read() or SSL_write() is called     directly. In that scenario, if the handshake fails then     a fatal error will be returned in the initial function     call. If SSL_read()/SSL_write() is subsequently called     by the application for the same SSL object then it will     succeed and the data is passed without being     decrypted/encrypted directly from the SSL/TLS record     layer. In order to exploit this issue an application bug     would have to be present that resulted in a call to     SSL_read()/SSL_write() being issued after having already     received a fatal error. OpenSSL version 1.0.2b-1.0.2m     are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is     not affected. (bsc#1071905)

  - CVE-2017-3738: There is an overflow bug in the AVX2     Montgomery multiplication procedure used in     exponentiation with 1024-bit moduli. No EC algorithms     are affected. Analysis suggests that attacks against RSA     and DSA as a result of this defect would be very     difficult to perform and are not believed likely.
    Attacks against DH1024 are considered just feasible,     because most of the work necessary to deduce information     about a private key may be performed offline. The amount     of resources required for such an attack would be     significant. However, for an attack on TLS to be     meaningful, the server would have to share the DH1024     private key among multiple clients, which is no longer     an option since CVE-2016-0701. This only affects     processors that support the AVX2 but not ADX extensions     like Intel Haswell (4th generation). Note: The impact     from this issue is similar to CVE-2017-3736,     CVE-2017-3732 and CVE-2015-3193. (bsc#1071906)

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.

According to the versions of the openssl packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - A NULL pointer dereference flaw was found in OpenSSL's     X.509 certificate handling implementation. A specially     crafted X.509 certificate could cause an application     using OpenSSL to crash if the application attempted to     convert the certificate to a certificate     request.(CVE-2015-0288)

  - Off-by-one error in the DTLS implementation in OpenSSL     0.9.8 before 0.9.8f allows remote attackers to execute     arbitrary code via unspecified vectors.(CVE-2007-4995)

  - An integer underflow flaw, leading to a buffer     overflow, was found in the way OpenSSL decoded     malformed Base64-encoded inputs. An attacker able to     make an application using OpenSSL decode a specially     crafted Base64-encoded input (such as a PEM file) could     use this flaw to cause the application to crash. Note:
    this flaw is not exploitable via the TLS/SSL protocol     because the data being transferred is not     Base64-encoded.(CVE-2015-0292)

  - OpenSSL before 0.9.8q, and 1.0.x before 1.0.0c, when     SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG is enabled,     does not properly prevent modification of the     ciphersuite in the session cache, which allows remote     attackers to force the downgrade to an unintended     cipher via vectors involving sniffing network traffic     to discover a session identifier.(CVE-2010-4180)

  - OpenSSL before 0.9.8m does not check for a NULL return     value from bn_wexpand function calls in (1)     crypto/bn/bn_div.c, (2) crypto/bn/bn_gf2m.c, (3)     crypto/ec/ec2_smpl.c, and (4) engines/e_ubsec.c, which     has unspecified impact and context-dependent attack     vectors.(CVE-2009-3245)

  - The Cryptographic Message Syntax (CMS) implementation     in crypto/cms/cms_asn1.c in OpenSSL before 0.9.8o and     1.x before 1.0.0a does not properly handle structures     that contain OriginatorInfo, which allows     context-dependent attackers to modify invalid memory     locations or conduct double-free attacks, and possibly     execute arbitrary code, via unspecified     vectors.(CVE-2010-0742)

  - Race condition in the ssl3_read_bytes function in     s3_pkt.c in OpenSSL through 1.0.1g, when     SSL_MODE_RELEASE_BUFFERS is enabled, allows remote     attackers to inject data across sessions or cause a     denial of service (use-after-free and parsing error)     via an SSL connection in a multithreaded     environment.(CVE-2010-5298)

  - The BN_from_montgomery function in crypto/bn/bn_mont.c     in OpenSSL 0.9.8e and earlier does not properly perform     Montgomery multiplication, which might allow local     users to conduct a side-channel attack and retrieve RSA     private keys.(CVE-2007-3108)

  - A memory leak flaw was found in the way an OpenSSL     handled failed session ticket integrity checks. A     remote attacker could exhaust all available memory of     an SSL/TLS or DTLS server by sending a large number of     invalid session tickets to that server.(CVE-2014-3567)

  - It was discovered that OpenSSL would perform an ECDH     key exchange with a non-ephemeral key even when the     ephemeral ECDH cipher suite was selected. A malicious     server could make a TLS/SSL client using OpenSSL use a     weaker key exchange method than the one requested by     the user.(CVE-2014-3572)

  - A denial of service flaw was found in the way OpenSSL     handled certain DTLS ServerHello requests. A specially     crafted DTLS handshake packet could cause a DTLS client     using OpenSSL to crash.(CVE-2014-0221)

  - A NULL pointer dereference was found in the way OpenSSL     handled certain PKCS#7 inputs. An attacker able to make     an application using OpenSSL verify, decrypt, or parse     a specially crafted PKCS#7 input could cause that     application to crash. TLS/SSL clients and servers using     OpenSSL were not affected by this flaw.(CVE-2015-1790)

  - The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0     and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and     other products, do not properly consider timing     side-channel attacks on a MAC check requirement during     the processing of malformed CBC padding, which allows     remote attackers to conduct distinguishing attacks and     plaintext-recovery attacks via statistical analysis of     timing data for crafted packets, aka the 'Lucky     Thirteen' issue.(CVE-2013-0169)

  - OpenSSL 0.9.8i and earlier does not properly check the     return value from the EVP_VerifyFinal function, which     allows remote attackers to bypass validation of the     certificate chain via a malformed SSL/TLS signature for     DSA and ECDSA keys.(CVE-2008-5077)

  - The TLS protocol, and the SSL protocol 3.0 and possibly     earlier, as used in Microsoft Internet Information     Services (IIS) 7.0, mod_ssl in the Apache HTTP Server     2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5     and earlier, Mozilla Network Security Services (NSS)     3.12.4 and earlier, multiple Cisco products, and other     products, does not properly associate renegotiation     handshakes with an existing connection, which allows     man-in-the-middle attackers to insert data into HTTPS     sessions, and possibly other types of sessions     protected by TLS or SSL, by sending an unauthenticated     request that is processed retroactively by a server in     a post-renegotiation context, related to a 'plaintext     injection' attack, aka the 'Project Mogul'     issue.(CVE-2009-3555)

  - Multiple memory leaks in the     dtls1_process_out_of_seq_message function in     ssl/d1_both.c in OpenSSL 0.9.8k and earlier 0.9.8     versions allow remote attackers to cause a denial of     service (memory consumption) via DTLS records that (1)     are duplicates or (2) have sequence numbers much     greater than current sequence numbers, aka 'DTLS     fragment handling memory leak.'(CVE-2009-1378)

  - The dtls1_retrieve_buffered_fragment function in     ssl/d1_both.c in OpenSSL before 1.0.0 Beta 2 allows     remote attackers to cause a denial of service (NULL     pointer dereference and daemon crash) via an     out-of-sequence DTLS handshake message, related to a     'fragment bug.'(CVE-2009-1387)

  - There is a carry propagating bug in the x86_64     Montgomery squaring procedure in OpenSSL before 1.0.2m     and 1.1.0 before 1.1.0g. No EC algorithms are affected.
    Analysis suggests that attacks against RSA and DSA as a     result of this defect would be very difficult to     perform and are not believed likely. Attacks against DH     are considered just feasible (although very difficult)     because most of the work necessary to deduce     information about a private key may be performed     offline. The amount of resources required for such an     attack would be very significant and likely only     accessible to a limited number of attackers. An     attacker would additionally need online access to an     unpatched system using the target private key in a     scenario with persistent DH parameters and a private     key that is shared between multiple clients. This only     affects processors that support the BMI1, BMI2 and ADX     extensions like Intel Broadwell (5th generation) and     later or AMD Ryzen.(CVE-2017-3736)

  - A flaw was discovered in the way OpenSSL handled DTLS     packets. A remote attacker could use this flaw to cause     a DTLS server or client using OpenSSL to crash or use     excessive amounts of memory.(CVE-2014-3505)

  - The dtls1_reassemble_fragment function in d1_both.c in     OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1     before 1.0.1h does not properly validate fragment     lengths in DTLS ClientHello messages, which allows     remote attackers to execute arbitrary code or cause a     denial of service (buffer overflow and application     crash) via a long non-initial fragment.(CVE-2014-0195)

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.

ID	Name	Product	Family	Published	Updated	Severity
117700	SUSE SLES12 Security Update : java-1_8_0-ibm (SUSE-SU-2018:2839-1)	Nessus	SuSE Local Security Checks	9/25/2018	3/25/2022	critical
105341	openSUSE Security Update : openssl (openSUSE-2017-1381)	Nessus	SuSE Local Security Checks	12/18/2017	1/19/2021	medium
105353	SUSE SLED12 / SLES12 Security Update : openssl (SUSE-SU-2017:3343-1)	Nessus	SuSE Local Security Checks	12/18/2017	1/6/2021	medium
125000	EulerOS Virtualization 3.0.1.0 : openssl (EulerOS-SA-2019-1547)	Nessus	Huawei Local Security Checks	5/14/2019	5/22/2024	medium

Detections

Analytics

Plugins Search

critical

medium

medium

medium