Direct Use of Unsafe JNI

Every one of the 2 is a mark on the map. Named now: 1 to 2, most at risk first.

1. In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when accelerating it.CVE-2018-12549The Eclipse Foundation · 2.3% likely

   Eclipse Foundation

2. A vulnerability in SIEMENS SIMATIC WinCC (All versions < SIMATIC WinCC V7.2) and SIEMENS SIMATIC PCS 7 (All versions < SIMATIC PCS 7 V8.0 SP1) could allow a remote attacker to cra…CVE-2016-9160Siemens · 1.4% likely

   Siemens

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.