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.
                
            References
                    | Link | Resource | 
|---|---|
| https://github.com/eclipse-openj9/openj9/pull/16122 | Patch Third Party Advisory | 
| https://github.com/eclipse/omr/pull/6773 | Patch Third Party Advisory | 
| https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 | Issue Tracking Vendor Advisory | 
| https://github.com/eclipse-openj9/openj9/pull/16122 | Patch Third Party Advisory | 
| https://github.com/eclipse/omr/pull/6773 | Patch Third Party Advisory | 
| https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 | Issue Tracking Vendor Advisory | 
Configurations
                    History
                    21 Nov 2024, 07:20
| Type | Values Removed | Values Added | 
|---|---|---|
| References | () https://github.com/eclipse-openj9/openj9/pull/16122 - Patch, Third Party Advisory | |
| References | () https://github.com/eclipse/omr/pull/6773 - Patch, Third Party Advisory | |
| References | () https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 - Issue Tracking, Vendor Advisory | 
Information
                Published : 2022-10-24 14:15
Updated : 2025-05-07 16:15
NVD link : CVE-2022-3676
Mitre link : CVE-2022-3676
CVE.ORG link : CVE-2022-3676
JSON object : View
Products Affected
                eclipse
- openj9
