# CVE-2022-3676: Memory corruption in Eclipse OpenJ9 > Attackers can exploit missing runtime type checks in Eclipse OpenJ9 to access or modify memory via malicious bytecode, potentially leading to code execution. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Oct 2022 - **Updated:** 7 May 2025 - **Also known as:** GHSA-vw7j-6j6f-vm86, SUSE-SU-2022:4591-1, SUSE-SU-2022:4602-1, SUSE-SU-2023:0375-1 ## What is CVE-2022-3676? CVE-2022-3676 is a medium-severity memory corruption vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 24 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2022-3676? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `java-1_8_0-ibm` | SUSE:Enterprise Storage 6 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Enterprise Storage 7 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Enterprise Storage 7.1 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Module for Legacy 15 SP4 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 1.8.0_sr7.20-150000.3.68.1 | | `java-1_7_1-ibm` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_7_1-ibm` | SUSE:OpenStack Cloud 9 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:OpenStack Cloud 9 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_7_1-ibm` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 1.7.1_sr5.15-38.77.1 | | `java-1_8_0-ibm` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 1.8.0_sr7.20-30.102.1 | | `java-1_8_0-ibm` | openSUSE:Leap 15.4 | All versions | 1.8.0_sr7.20-150000.3.68.1 | Products: Eclipse Openj9. ## How do I fix CVE-2022-3676? Upgrade to a fixed version. ## Is CVE-2022-3676 being exploited? There is no known exploitation of CVE-2022-3676 in the wild and no public exploit code. ## Other vulnerabilities in The Eclipse Foundation Eclipse OpenJ9 - [CVE-2021-41035](https://insights.sbomify.com/CVE-2021-41035/): Security feature bypass in Eclipse OMR (critical 9.8) - [CVE-2020-27221](https://insights.sbomify.com/CVE-2020-27221/): Memory corruption in Eclipse OpenJ9 (critical 9.8) - [CVE-2019-11772](https://insights.sbomify.com/CVE-2019-11772/): Memory corruption in Eclipse OpenJ9 (critical 9.8) - [CVE-2018-12547](https://insights.sbomify.com/CVE-2018-12547/): Memory corruption in Eclipse OpenJ9 (critical 9.8) - [CVE-2018-12549](https://insights.sbomify.com/CVE-2018-12549/): Null dereference in Eclipse OpenJ9 (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-3676 and fix it if it is affected. What it is: CVE-2022-3676 is a medium-severity memory corruption vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 24 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-3676 in the wild and no public exploit code. Affected product: The Eclipse Foundation Eclipse OpenJ9. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-3676/ (Markdown: https://insights.sbomify.com/CVE-2022-3676/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3676 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3676 - OSV: https://osv.dev/vulnerability/CVE-2022-3676 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-3676/ Summaries are generated and may contain mistakes; the official description above is the record.