Vulnerability Description
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.
CVSS Score
6.5
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Eclipse | Openj9 | < 0.35.0 |
Related Weaknesses (CWE)
References
- https://github.com/eclipse-openj9/openj9/pull/16122PatchThird Party Advisory
- https://github.com/eclipse/omr/pull/6773PatchThird Party Advisory
- https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389Issue TrackingVendor Advisory
- https://github.com/eclipse-openj9/openj9/pull/16122PatchThird Party Advisory
- https://github.com/eclipse/omr/pull/6773PatchThird Party Advisory
- https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389Issue TrackingVendor Advisory
FAQ
What is CVE-2022-3676?
CVE-2022-3676 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 ...
How severe is CVE-2022-3676?
CVE-2022-3676 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-3676?
Check the references section above for vendor advisories and patch information. Affected products include: Eclipse Openj9.