Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Libraries). CVSS 3.1 Base Score 4.2 (Confidentiality and Integrity impacts). 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. This vulnerability can be exploited through sandboxed Java Web Start applications and sandboxed Java applets. Note: Applies to client and server deployment of Java. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Java SE, Java SE Embedded accessible data as well as unauthorized read access to a subset of Java SE, Java SE Embedded accessible data. Successful attacks require human interaction from a person other than the attacker. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. Supported versions that are affected are Java SE: 7u271, 8u261, 11.0.8 and 15 Java SE Embedded: 8u261. Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Hotspot). OpenSSL 1.0.2 is not impacted by this issue. #Download Mcafee Unlock User Interface Regedit upgradeUsers of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL versions 1.1.1h and newer are affected by this issue. #Download Mcafee Unlock User Interface Regedit verificationIn order to be affected, an application must explicitly set the X509_V_FLAG_X509_STRICT verification flag and either not set a purpose for the certificate verification or, in the case of TLS client or server applications, override the default purpose. A purpose is set by default in libssl client and server certificate verification routines, but it can be overridden or removed by an application. Therefore, where a purpose is set the certificate chain will still be rejected even when the strict flag has been used. All of the named "purpose" values implemented in libcrypto perform this check. If a "purpose" has been configured then there is a subsequent opportunity for checks that the certificate is a valid CA. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates. An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |