In Eclipse Openj9 before version 0.35.0, interface calls can be inlined without a runtime type check. Malicious bytecode could make use of this inlining to access or modify memory via an incompatible type.
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.
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
Link | Tags |
---|---|
https://github.com/eclipse-openj9/openj9/pull/16122 | third party advisory patch |
https://github.com/eclipse/omr/pull/6773 | third party advisory patch |
https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 | vendor advisory issue tracking |