Eclipse OpenJ9 up to 0.20 System.arraycopy Return Value type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Eclipse OpenJ9 up to 0.20. The impacted element is an unknown function of the file System.arraycopy. Performing a manipulation as part of Return Value results in type confusion. This vulnerability is reported as CVE-2019-17639. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Eclipse OpenJ9 up to 0.20. This affects some unknown functionality of the file System.arraycopy. The manipulation as part of a Return Value leads to a type confusion vulnerability. CWE is classifying the issue as CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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 source or destination array can, in certain specially crafted code patterns, cause the current method to return prematurely with an undefined return value. This allows whatever value happens to be in the return register at that time to be used as if it matches the method's declared return type.
The weakness was disclosed 07/15/2020 (Website). The advisory is shared at bugs.eclipse.org. This vulnerability is uniquely identified as CVE-2019-17639 since 10/16/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 208630 (CentOS 6 : java-1.7.1-ibm (RHSA-2020:3387)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.21 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (208630). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Type confusionCWE: CWE-843
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 208630
Nessus Name: CentOS 6 : java-1.7.1-ibm (RHSA-2020:3387)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OpenJ9 0.21
Timeline
10/16/2019 🔍07/15/2020 🔍
07/16/2020 🔍
10/12/2024 🔍
Sources
Advisory: bugs.eclipse.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-17639 (🔍)
GCVE (CVE): GCVE-0-2019-17639
GCVE (VulDB): GCVE-100-158517
Entry
Created: 07/16/2020 10:48Updated: 10/12/2024 19:13
Changes: 07/16/2020 10:48 (40), 07/16/2020 10:53 (17), 11/02/2020 22:47 (1), 10/12/2024 19:13 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.