Skip to content
Noroxi
NVD / CVE Program· CNA eclipse

CVE-2020-27221: In Eclipse OpenJ9 up to and including version 0.23, there is potential for a stack-based buffer overflow when the virtual machine or JNI nat

Noroxi assessment

Priority: Monitor (action score 39/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: 1.5% (FIRST EPSS); higher than 75.2% 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.6.25-2.el8_3; java-1.8.0-ibm-demo (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.6.25-2.el8_3; java-1.8.0-ibm-devel (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.6.25-2.el8_3.
  • Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to java-1.8.0-ibm (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.6.25-2.el8_3; java-1.8.0-ibm-demo (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.6.25-2.el8_3; java-1.8.0-ibm-devel (Red Hat:enterprise_linux:8::supplementary) 1:1.8.0.6.25-2.el8_3 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

Primary sources: NVD · CVE.org · FIRST EPSS

In Eclipse OpenJ9 up to and including version 0.23, there is potential for a stack-based buffer overflow when the virtual machine or JNI natives are converting from UTF-8 characters to platform encoding.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Jan 21, 2021
Updated
Jun 16, 2026
EPSS
1.5% · 75th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

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.

Follow CVE-2020-27221

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for eclipse records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
eclipseopenj9

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • eclipse openj9up to 0.23.0 inclusive

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

    • unspecified and later · up to and including 0.23affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibmbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-demobefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-develbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-headlessbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-jdbcbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-pluginbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-srcbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:enterprise_linux:8::supplementaryjava-1.8.0-ibm-webstartbefore 1:1.8.0.6.25-2.el8_31:1.8.0.6.25-2.el8_3
Red Hat:rhel_extras:7java-1.7.1-ibmbefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.7.1-ibm-demobefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.7.1-ibm-develbefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.7.1-ibm-jdbcbefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.7.1-ibm-pluginbefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.7.1-ibm-srcbefore 1:1.7.1.4.80-1jpp.1.el71:1.7.1.4.80-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibmbefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibm-demobefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibm-develbefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibm-jdbcbefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibm-pluginbefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
Red Hat:rhel_extras:7java-1.8.0-ibm-srcbefore 1:1.8.0.6.25-1jpp.1.el71:1.8.0.6.25-1jpp.1.el7
SUSE:HPE Helion OpenStack 8java-1_7_1-ibmbefore 1.7.1_sr4.80-38.62.11.7.1_sr4.80-38.62.1
SUSE:HPE Helion OpenStack 8java-1_8_0-ibmbefore 1.8.0_sr6.25-30.81.11.8.0_sr6.25-30.81.1
SUSE:Linux Enterprise Module for Legacy 15 SP2java-1_8_0-ibmbefore 1.8.0_sr6.25-3.50.11.8.0_sr6.25-3.50.1
SUSE:Linux Enterprise Point of Sale 11 SP3java-1_7_0-ibmbefore 1.7.0_sr10.80-65.60.11.7.0_sr10.80-65.60.1

+1

Same product

eclipse: all records

Other 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 meth
    40Plan
  • 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-12549In 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
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2019-17631Oct 17, 2019 · From Eclipse OpenJ9 0.15 to 0.16, access to diagnostic operations such as causing a GC or creating a diagnostic file are permitted without a
    37Monitor
  • ← EarlierCVE-2019-17639Jul 15, 2020 · In Eclipse OpenJ9 prior to version 0.21 on Power platforms, calling the System.arraycopy method with a length longer than the length of the
    21Monitor
  • Later →CVE-2021-28167Apr 21, 2021 · In Eclipse Openj9 to version 0.25.0, usage of the jdk.internal.reflect.ConstantPool API causes the JVM in some cases to pre-resolve certain
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:java-1.7.1-ibm1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.7.1-ibm-demo1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.7.1-ibm-devel1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.7.1-ibm-jdbc1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.7.1-ibm-plugin1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.7.1-ibm-src1:1.7.1.4.80-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm-demo1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm-devel1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm-jdbc1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm-plugin1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
red hat:java-1.8.0-ibm-src1:1.8.0.6.25-1jpp.1.el7 · Red Hat:rhel_extras:7Package registry (OSV)
suse:java-1_7_0-ibm1.7.0_sr10.80-65.60.1 · SUSE:Linux Enterprise Point of Sale 11 SP3Package registry (OSV)
suse:java-1_7_1-ibm1.7.1_sr4.80-38.62.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:java-1_8_0-ibm1.8.0_sr6.25-30.81.1 · SUSE:HPE Helion OpenStack 8Package 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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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-121 · Stack-based Buffer Overflow

CVSS vector

CVSS:3.1/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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records