CVE-2022-3676 json
In Eclipse Openj9 before version 0.35.0, interface calls can be inlined without a runtime type check.
published 4y ago modified 4mo ago also EUVD-2022-43035
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- The Eclipse Foundation Eclipse OpenJ9 0.35.0
- java-1_8_0-ibm SLES for SAP 15 SP3, SLES for SAP 15 SP2, SLES for SAP 15 SP1 +10 more 1.8.0_sr7.20-150000.3.68.1
- java-1_8_0-ibm SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +5 more 1.8.0_sr7.20-30.102.1
- java-1_7_1-ibm SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +5 more 1.7.1_sr5.15-38.77.1
- java-1_8_0-openj9 openSUSE Leap 15.4, openSUSE Leap 15.3 1.8.0.352-150200.3.27.1
suse advisories SUSE-SU-2023:0375-1SUSE-SU-2022:4602-1SUSE-SU-2022:4591-1SUSE-SU-2022:4250-1
- java-17-openj9 Package Hub 15 SP6, openSUSE Leap 15.6 17.0.14.0-bp156.3.3.1
- java-11-openj9 Package Hub 15 SP6, openSUSE Leap 15.6 11.0.26.0-bp156.4.3.1
- java-11-openj9 openSUSE Tumbleweed 11.0.17.0-1.1
- java-17-openj9 openSUSE Tumbleweed 17.0.5.0-1.1
- java-1_8_0-openj9 openSUSE Tumbleweed 1.8.0.352-1.1
opensuse advisories openSUSE-SU-2025:0067-1openSUSE-SU-2025:0066-1openSUSE-SU-2024:12463-1openSUSE-SU-2024:12464-1openSUSE-SU-2024:12465-1
- github.com/eclipse-openj9/openj9#16122 pull request
- github.com/eclipse/omr#6773 pull request
Is CVE-2022-3676 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- The Eclipse Foundation Eclipse OpenJ9
Classification
References
-
github.com
/eclipse-openj9/openj9/pull/16122
patch, third-party-advisory
-
github.com
/eclipse/omr/pull/6773
patch, third-party-advisory
-
gitlab.eclipse.org
/eclipsefdn/emo-team/emo/-/issues/389
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2022-3676
- NVD CVE-2022-3676
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.