CVE-2020-7003 Vulnerability Analysis & Exploit Details

CVE-2020-7003
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2020-7003 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2020-7003 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:36 UTC
Originally published on: 🕕 24 Mar 2020, 18:15 UTC

Time between publication and last update: 1702 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE-2020-7003 Vulnerability Summary

CVE-2020-7003: In Moxa ioLogik 2500 series firmware, Version 3.0 or lower, and IOxpress configuration utility, Version 2.3.0 or lower, sensitive information is transmitted over some web applications in clear text.

Assessing the Risk of CVE-2020-7003

Access Complexity Graph

The exploitability of CVE-2020-7003 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2020-7003

With low attack complexity and no required privileges, CVE-2020-7003 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2020-7003, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2020-7003, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2020-7003 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2020-7003 poses no threat to data integrity.
  • Availability: None
    CVE-2020-7003 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.128% (probability of exploit)

EPSS Percentile: 48.97% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 51.03% of others.

CVE-2020-7003 References

External References

CWE Common Weakness Enumeration

CWE-319

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Sidejacking CAPEC-102 Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
  • Interception CAPEC-117 An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position themself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Adversary-In-the-Middle (CAPEC-94) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.
  • Harvesting Information via API Event Monitoring CAPEC-383 An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.
  • Signature Spoofing by Mixing Signed and Unsigned Content CAPEC-477 An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.
  • Sniff Application Code CAPEC-65 An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.

Vulnerable Configurations

  • cpe:2.3:o:moxa:iologik_2512_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-hspa_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-hspa_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-hspa_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-hspa_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-hspa:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-hspa:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-hspa-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-hspa-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-hspa-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-hspa-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-hspa-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-hspa-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-eu_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-eu_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-eu_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-eu_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-eu:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-eu:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-eu-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-eu-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-eu-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-eu-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-eu-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-eu-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-us_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-us_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-us_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-us_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-us:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-us:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-us-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-us-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-us-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-us-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-us-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-us-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-jp_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-jp_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-jp_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-jp_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-jp:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-jp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-jp-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-jp-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2512-wl1-jp-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2512-wl1-jp-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2512-wl1-jp-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2512-wl1-jp-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-hspa_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-hspa_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-hspa_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-hspa_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-hspa:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-hspa:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-hspa-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-hspa-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-hspa-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-hspa-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-hspa-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-hspa-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-eu_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-eu_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-eu:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-eu:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-eu-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-eu-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-eu-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-eu-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-us_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-us_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-us_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-us_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-us:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-us:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-us-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-us-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-us-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-us-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-us-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-us-t:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-jp_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-jp_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-jp_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-jp_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-jp:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-jp:-:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-jp-t_firmware:2.3:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-jp-t_firmware:2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:moxa:iologik_2542-wl1-jp-t_firmware:3.0:*:*:*:*:*:*:*
    cpe:2.3:o:moxa:iologik_2542-wl1-jp-t_firmware:3.0:*:*:*:*:*:*:*
  • cpe:2.3:h:moxa:iologik_2542-wl1-jp-t:-:*:*:*:*:*:*:*
    cpe:2.3:h:moxa:iologik_2542-wl1-jp-t:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2020-7003: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...