7 matches found
RHEL 7 : ibm_jdk (Unpatched Vulnerability)
The remote Redhat Enterprise Linux 7 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched. - IBM JDK: unsafe deserialization flaw in the Object Request Broker ORB CVE-2022-40609 - IBM JDK: Object...
CVE-2023-5676
Eclipse OpenJ9 is vulnerable to a denial of service, caused by a flaw when a shutdown signal SIGTERM, SIGINT or SIGHUP is received before the JVM has finished initializing. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause an infinite...
IBM Java 7.1 < 7.1.5.20 / 8.0 < 8.0.8.15
The version of IBM Java installed on the remote host is prior to 7.1 7.1.5.20 / 8.0 8.0.8.15. It is, therefore, affected by a vulnerability as referenced in the IBM Security Update November 2023 advisory. - In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang ...
CVE-2023-5676
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal SIGTERM, SIGINT or SIGHUP is received before the JVM has finished initializing...
CVE-2023-5676 Eclipse OpenJ9 possible infinite busy hang
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal SIGTERM, SIGINT or SIGHUP is received before the JVM has finished initializing...
CVE-2023-5676 Eclipse OpenJ9 possible infinite busy hang
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal SIGTERM, SIGINT or SIGHUP is received before the JVM has finished initializing...
CVE-2023-5676: Signal Handler Race Condition
In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal SIGTERM, SIGINT or SIGHUP is received before the JVM has finished initializing...