Memory disclosure and modification via unchecked interface inlining
Published Oct 24, 2022 · Updated May 7, 2025
Type confusion in Eclipse OpenJ9 before 0.35.0 allows remote attackers to access or modify memory using malicious bytecode. The JIT can inline or devirtualize an interface call without proving that its receiver implements the expected interface, so the callee accesses receiver fields as the wrong class. Triggering requires attacker-supplied bytecode and an affected JIT compilation path; the resulting incompatible field access is limited to memory disclosure or modification.
Summary
What happened
Type confusion in Eclipse OpenJ9 before 0.35.0 allows remote attackers to access or modify memory using malicious bytecode. The JIT can inline or devirtualize an interface call without proving that its receiver implements the expected interface, so the callee accesses receiver fields as the wrong class. Triggering requires attacker-supplied bytecode and an affected JIT compilation path; the resulting incompatible field access is limited to memory disclosure or modification.
The record
- CVE
- CVE-2022-3676
- Published
- Oct 24, 2022
- Updated
- May 7, 2025
- Vendor
- The Eclipse Foundation
- Product
- Eclipse OpenJ9
- Classifications
- CWE-843, CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 2022CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <0.35.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo