In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when ac
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.3% (FIRST EPSS); higher than 83% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: java-1.8.0-ibm (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0; java-1.8.0-ibm-demo (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0; java-1.8.0-ibm-devel (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0.
Add it to your regular patch cycle. Upgrade to java-1.8.0-ibm (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0; java-1.8.0-ibm-demo (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0; java-1.8.0-ibm-devel (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.5.35-3.el8_0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of an Unsafe call when accelerating it.
- Published
- Feb 11, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.3% · 83th percentile
- CWE
- CWE-111
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| eclipse | openj9 | cpe:2.3:a:eclipse:openj9 |
| redhat | satellite | cpe:2.3:a:redhat:satellite |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- eclipse openj90.11.0
- redhat enterprise linux desktop6.0
- redhat enterprise linux desktop7.0
- redhat enterprise linux server6.0
- redhat enterprise linux server7.0
- redhat enterprise linux workstation6.0
- redhat enterprise linux workstation7.0
- redhat satellite5.8
Versions reported by the vendor
Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.
The Eclipse Foundation Eclipse OpenJ9
- 0.11.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-demo | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-devel | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-headless | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-jdbc | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-plugin | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-src | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:enterprise_linux:8::supplementary | java-1.8.0-ibm-webstart | before 1:1.8.0.5.35-3.el8_0 | 1:1.8.0.5.35-3.el8_0 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm-demo | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm-devel | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm-jdbc | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm-plugin | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:6 | java-1.8.0-ibm-src | before 1:1.8.0.5.30-1jpp.1.el6_10 | 1:1.8.0.5.30-1jpp.1.el6_10 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm-demo | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm-devel | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm-jdbc | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm-plugin | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
| Red Hat:rhel_extras:7 | java-1.8.0-ibm-src | before 1:1.8.0.5.30-1jpp.1.el7 | 1:1.8.0.5.30-1jpp.1.el7 |
Same product
eclipse: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-41035In Eclipse Openj9 before version 0.29.0, the JVM does not throw IllegalAccessError for MethodHandles that invoke inaccessible interface meth40Plan
- CVE-2019-11772In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided byte array is non-null 40Plan
- CVE-2018-12547In Eclipse OpenJ9, prior to the 0.12.0 release, the jio_snprintf() and jio_vsnprintf() native methods ignored the length parameter.40Plan
- CVE-2020-27221In Eclipse OpenJ9 up to and including version 0.23, there is potential for a stack-based buffer overflow when the virtual machine or JNI nat39Monitor
- CVE-2018-12548In OpenJDK + Eclipse OpenJ9 version 0.11.0 builds, the public jdk.crypto.jniprovider.NativeCrypto class contains public static natives which39Monitor
- CVE-2019-17631From Eclipse OpenJ9 0.15 to 0.16, access to diagnostic operations such as causing a GC or creating a diagnostic file are permitted without a37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:java-1.8.0-ibm | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-demo | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-devel | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-headless | 1:1.8.0.5.35-3.el8_0 · Red Hat:enterprise_linux:8::supplementary | Package registry (OSV) |
| red hat:java-1.8.0-ibm-jdbc | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-plugin | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-src | 1:1.8.0.5.30-1jpp.1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:java-1.8.0-ibm-webstart | 1:1.8.0.5.35-3.el8_0 · Red Hat:enterprise_linux:8::supplementary | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-111 · Direct Use of Unsafe JNICVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.