CVE-2021-20588 : Détail

CVE-2021-20588

9.8
/
Critique
Overflow
2.33%V4
Network
2021-02-19
19h58 +00:00
2024-08-03
17h45 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

Improper handling of length parameter inconsistency vulnerability in Mitsubishi Electric FA Engineering Software(CPU Module Logging Configuration Tool versions 1.112R and prior, CW Configurator versions 1.011M and prior, Data Transfer versions 3.44W and prior, EZSocket versions 5.4 and prior, FR Configurator all versions, FR Configurator SW3 all versions, FR Configurator2 versions 1.24A and prior, GT Designer3 Version1(GOT1000) versions 1.250L and prior, GT Designer3 Version1(GOT2000) versions 1.250L and prior, GT SoftGOT1000 Version3 versions 3.245F and prior, GT SoftGOT2000 Version1 versions 1.250L and prior, GX Configurator-DP versions 7.14Q and prior, GX Configurator-QP all versions, GX Developer versions 8.506C and prior, GX Explorer all versions, GX IEC Developer all versions, GX LogViewer versions 1.115U and prior, GX RemoteService-I all versions, GX Works2 versions 1.597X and prior, GX Works3 versions 1.070Y and prior, iQ Monozukuri ANDON (Data Transfer) all versions, iQ Monozukuri Process Remote Monitoring (Data Transfer) all versions, M_CommDTM-HART all versions, M_CommDTM-IO-Link versions 1.03D and prior, MELFA-Works versions 4.4 and prior, MELSEC WinCPU Setting Utility all versions, MELSOFT EM Software Development Kit (EM Configurator) versions 1.015R and prior, MELSOFT Navigator versions 2.74C and prior, MH11 SettingTool Version2 versions 2.004E and prior, MI Configurator versions 1.004E and prior, MT Works2 versions 1.167Z and prior, MX Component versions 5.001B and prior, Network Interface Board CC IE Control utility versions 1.29F and prior, Network Interface Board CC IE Field Utility versions 1.16S and prior, Network Interface Board CC-Link Ver.2 Utility versions 1.23Z and prior, Network Interface Board MNETH utility versions 34L and prior, PX Developer versions 1.53F and prior, RT ToolBox2 versions 3.73B and prior, RT ToolBox3 versions 1.82L and prior, Setting/monitoring tools for the C Controller module (SW4PVC-CCPU) versions 4.12N and prior and SLMP Data Collector versions 1.04E and prior) allows a remote unauthenticated attacker to cause a DoS condition of the software products, and possibly to execute a malicious program on the personal computer running the software products although it has not been reproduced, by spoofing MELSEC, GOT or FREQROL and returning crafted reply packets.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.1 9.8 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 nvd@nist.gov
V2 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P nvd@nist.gov

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

Score EPSS

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Percentile EPSS

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Mitsubishielectric>>C_controller_module_setting_and_monitoring_tool >> Version *

  • Mitsubishielectric>>C_controller_module_setting_and_monitoring_tool >> Version - (Open CPE detail)

Mitsubishielectric>>Cpu_module_logging_configuration_tool >> Version To (including) 1.112r

  • Mitsubishielectric>>Cpu_module_logging_configuration_tool >> Version - (Open CPE detail)
  • Mitsubishielectric>>Cpu_module_logging_configuration_tool >> Version 1.94y (Open CPE detail)
  • Mitsubishielectric>>Cpu_module_logging_configuration_tool >> Version 1.100e (Open CPE detail)
  • Mitsubishielectric>>Cpu_module_logging_configuration_tool >> Version 1.106k (Open CPE detail)

Mitsubishielectric>>Cw_configurator >> Version To (including) 1.011m

Mitsubishielectric>>Data_transfer >> Version To (including) 3.44w

Mitsubishielectric>>Ezsocket >> Version *

Mitsubishielectric>>Fr_configurator >> Version *

Mitsubishielectric>>Fr_configurator_sw3 >> Version *

Mitsubishielectric>>Fr_configurator2 >> Version To (including) 1.24a

Mitsubishielectric>>Gt_designer3 >> Version To (including) 1.250l

Mitsubishielectric>>Gt_softgot1000 >> Version To (including) 3.245f

Mitsubishielectric>>Gt_softgot2000 >> Version To (including) 1.250l

Mitsubishielectric>>Gx_configurator-dp >> Version To (including) 7.14q

Mitsubishielectric>>Gx_configurator-qp >> Version *

Mitsubishielectric>>Gx_developer >> Version To (including) 8.506c

Mitsubishielectric>>Gx_explorer >> Version *

Mitsubishielectric>>Gx_iec_developer >> Version *

Mitsubishielectric>>Gx_logviewer >> Version To (including) 1.115u

Mitsubishielectric>>Gx_remoteservice-i >> Version *

Mitsubishielectric>>Gx_works2 >> Version To (including) 1.597x

Mitsubishielectric>>Gx_works3 >> Version To (including) 1.070y

Mitsubishielectric>>Iq_monozukuri_andon >> Version -

Mitsubishielectric>>Iq_monozukuri_process_remote_monitoring >> Version -

  • Mitsubishielectric>>Iq_monozukuri_process_remote_monitoring >> Version - (Open CPE detail)

Mitsubishielectric>>M_commdtm-hart >> Version *

Mitsubishielectric>>M_commdtm-io-link >> Version *

Mitsubishielectric>>Melfa-works >> Version To (including) 4.4

Mitsubishielectric>>Melsec_wincpu_setting_utility >> Version *

Mitsubishielectric>>Melsoft_em_software_development_kit >> Version *

Mitsubishielectric>>Melsoft_navigator >> Version To (including) 2.74c

Mitsubishielectric>>Mh11_settingtool_version2 >> Version To (including) 2.004e

Mitsubishielectric>>Mi_configurator >> Version *

Mitsubishielectric>>Mt_works2 >> Version To (including) 1.167z

Mitsubishielectric>>Mx_component >> Version To (including) 5.001b

Mitsubishielectric>>Network_interface_board_cc-link >> Version *

Mitsubishielectric>>Network_interface_board_cc_ie_control_utility >> Version *

  • Mitsubishielectric>>Network_interface_board_cc_ie_control_utility >> Version - (Open CPE detail)
  • Mitsubishielectric>>Network_interface_board_cc_ie_control_utility >> Version 1.30g (Open CPE detail)

Mitsubishielectric>>Network_interface_board_cc_ie_field_utility >> Version *

  • Mitsubishielectric>>Network_interface_board_cc_ie_field_utility >> Version - (Open CPE detail)
  • Mitsubishielectric>>Network_interface_board_cc_ie_field_utility >> Version 1.17t (Open CPE detail)

Mitsubishielectric>>Network_interface_board_mneth_utility >> Version *

Mitsubishielectric>>Px_developer >> Version To (including) 1.53f

Mitsubishielectric>>Rt_toolbox2 >> Version To (including) 3.73b

Mitsubishielectric>>Rt_toolbox3 >> Version To (including) 1.82l

Mitsubishielectric>>Setting\/monitoring_tools_for_the_c_controller_module >> Version *

  • Mitsubishielectric>>Setting\/monitoring_tools_for_the_c_controller_module >> Version - (Open CPE detail)

Mitsubishielectric>>Slmp_data_collector >> Version To (including) 1.04e

Références

Les informations affichées sur CVE Find proviennent de plusieurs sources de référence rigoureusement sélectionnées. Les données CVE sont fournies par MITRE Corporation et la National Vulnerability Database (NVD). Le catalogue des vulnérabilités activement exploitées (KEV) provient de la Cybersecurity and Infrastructure Security Agency (CISA), tandis que les scores EPSS sont issus de FIRST.org. Enfin, les données relatives aux faiblesses logicielles (CWE) et aux schémas d'attaque courants (CAPEC) sont maintenues par MITRE Corporation, et les informations sur les configurations logicielles et matérielles (CPE) proviennent du NVD.