Vulnerability record · CVE-2022-3676 · published 24 October 2022
CVE-2022-3676: Eclipse openj9 improper input validation vulnerability
Eclipse · Openj9
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.
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://github.com/eclipse-openj9/openj9/pull/16122 | PatchThird Party Advisory |
| https://github.com/eclipse/omr/pull/6773 | PatchThird Party Advisory |
| https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 | Issue TrackingVendor Advisory |
| https://github.com/eclipse-openj9/openj9/pull/16122 | PatchThird Party Advisory |
| https://github.com/eclipse/omr/pull/6773 | PatchThird Party Advisory |
| https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 | Issue TrackingVendor Advisory |
Track CVE-2022-3676 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2022-3676), CISA KEV, FIRST EPSS (scores of 2026-09-29). This page is refreshed as NVD updates the record.