Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • EMO EMO
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 118
    • Issues 118
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse FoundationEclipse Foundation
  • EMO TeamEMO Team
  • EMOEMO
  • Issues
  • #389
Closed
Open
Issue created Oct 19, 2022 by Peter Shipton@pshipton

CVE Request: technology.openj9 OpenJ9 may inline an interface call incorrectly, allowing type confusion

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.

Basic information

Project name: OpenJ9

Project id: technology.openj9

Versions affected: [Initial - 0.35.0)

Common Weakness Enumeration:

  • CWE-20: Improper Input Validation
  • CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')

Common Vulnerability Scoring System: {cvss}

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.

Links:

  • Disallow nop guards for interface call sites
  • Stop devirtualizing interface calls in preexistence

Tracking

This section will completed by the project team.

  • We're ready for this issue to be reported to the central authority (i.e., make this public now)
  • (when applicable) The GitHub Security Advisory is ready to be published now

Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.

This section will be completed by the EMO.

CVE: {cve}

  • All required information is provided
  • CVE Assigned
  • Pushed to Mitre
  • Accepted by Mitre
Edited Oct 24, 2022 by Mikaël Barbero
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent