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.
When a Java application uses the Java Native Interface (JNI) to call code written in another programming language, it can expose the application to weaknesses in that code, even if those weaknesses cannot occur in Java.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2019:0469 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:0472 | third party advisory vendor advisory |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=544019 | issue tracking vendor advisory mitigation |
https://access.redhat.com/errata/RHSA-2019:0640 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:1238 | vendor advisory |