CVE-2020-2509 : Detail

CVE-2020-2509

9.8
/
Critical
Command InjectionOS Command Injection
A03-Injection
0.29%V3
Network
2021-04-17
03h50 +00:00
2025-02-13
16h27 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Command Injection Vulnerability in QTS and QuTS hero

A command injection vulnerability has been reported to affect QTS and QuTS hero. If exploited, this vulnerability allows attackers to execute arbitrary commands in a compromised application. We have already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later QTS 4.5.1.1495 Build 20201123 and later QTS 4.3.6.1620 Build 20210322 and later QTS 4.3.4.1632 Build 20210324 and later QTS 4.3.3.1624 Build 20210416 and later QTS 4.2.6 Build 20210327 and later QuTS hero h4.5.1.1491 build 20201119 and later

CVE Solutions

QNAP has already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later QTS 4.5.1.1495 Build 20201123 and later QTS 4.3.6.1620 Build 20210322 and later QTS 4.3.4.1632 Build 20210324 and later QTS 4.3.3.1624 Build 20210416 and later QTS 4.2.6 Build 20210327 and later QuTS hero h4.5.1.1491 build 20201119 and later

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Metrics

Metrics Score Severity CVSS Vector 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.

 [email protected]
V2 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P [email protected]

CISA KEV (Known Exploited Vulnerabilities)

Vulnerability name : QNAP Network-Attached Storage (NAS) Command Injection Vulnerability

Required action : Apply updates per vendor instructions.

Known To Be Used in Ransomware Campaigns : Unknown

Added : 2022-04-10 22h00 +00:00

Action is due : 2022-05-01 22h00 +00:00

Important information
This CVE is identified as vulnerable and poses an active threat, according to the Catalog of Known Exploited Vulnerabilities (CISA KEV). The CISA has listed this vulnerability as actively exploited by cybercriminals, emphasizing the importance of taking immediate action to address this flaw. It is imperative to prioritize the update and remediation of this CVE to protect systems against potential cyberattacks.

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Qnap>>Qts >> Version To (excluding) 4.2.6

Qnap>>Qts >> Version From (including) 4.3.5 To (excluding) 4.3.6

Qnap>>Qts >> Version From (including) 4.4.0 To (excluding) 4.5.1

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.2.6

Qnap>>Qts >> Version 4.3.3.0174

Qnap>>Qts >> Version 4.3.3.0868

Qnap>>Qts >> Version 4.3.3.0998

Qnap>>Qts >> Version 4.3.3.1051

Qnap>>Qts >> Version 4.3.3.1098

Qnap>>Qts >> Version 4.3.3.1161

Qnap>>Qts >> Version 4.3.3.1252

Qnap>>Qts >> Version 4.3.3.1315

Qnap>>Qts >> Version 4.3.3.1386

Qnap>>Qts >> Version 4.3.3.1432

Qnap>>Qts >> Version 4.3.4.0358

Qnap>>Qts >> Version 4.3.4.0358

Qnap>>Qts >> Version 4.3.4.0370

Qnap>>Qts >> Version 4.3.4.0370

Qnap>>Qts >> Version 4.3.4.0372

Qnap>>Qts >> Version 4.3.4.0372

Qnap>>Qts >> Version 4.3.4.0374

Qnap>>Qts >> Version 4.3.4.0374

Qnap>>Qts >> Version 4.3.4.0387

Qnap>>Qts >> Version 4.3.4.0387

Qnap>>Qts >> Version 4.3.4.0411

Qnap>>Qts >> Version 4.3.4.0416

Qnap>>Qts >> Version 4.3.4.0427

Qnap>>Qts >> Version 4.3.4.0434

Qnap>>Qts >> Version 4.3.4.0435

Qnap>>Qts >> Version 4.3.4.0451

Qnap>>Qts >> Version 4.3.4.0483

Qnap>>Qts >> Version 4.3.4.0486

Qnap>>Qts >> Version 4.3.4.0506

Qnap>>Qts >> Version 4.3.4.0516

Qnap>>Qts >> Version 4.3.4.0526

Qnap>>Qts >> Version 4.3.4.0551

Qnap>>Qts >> Version 4.3.4.0557

Qnap>>Qts >> Version 4.3.4.0561

Qnap>>Qts >> Version 4.3.4.0569

Qnap>>Qts >> Version 4.3.4.0593

Qnap>>Qts >> Version 4.3.4.0597

Qnap>>Qts >> Version 4.3.4.0604

Qnap>>Qts >> Version 4.3.4.0899

Qnap>>Qts >> Version 4.3.4.1029

Qnap>>Qts >> Version 4.3.4.1082

Qnap>>Qts >> Version 4.3.4.1190

Qnap>>Qts >> Version 4.3.4.1282

Qnap>>Qts >> Version 4.3.4.1368

Qnap>>Qts >> Version 4.3.4.1417

Qnap>>Qts >> Version 4.3.4.1463

Qnap>>Qts >> Version 4.3.6

Qnap>>Qts >> Version 4.3.6.0895

Qnap>>Qts >> Version 4.3.6.0907

Qnap>>Qts >> Version 4.3.6.0923

Qnap>>Qts >> Version 4.3.6.0944

Qnap>>Qts >> Version 4.3.6.0959

Qnap>>Qts >> Version 4.3.6.0979

Qnap>>Qts >> Version 4.3.6.0993

Qnap>>Qts >> Version 4.3.6.1013

Qnap>>Qts >> Version 4.3.6.1033

Qnap>>Qts >> Version 4.3.6.1070

Qnap>>Qts >> Version 4.3.6.1154

Qnap>>Qts >> Version 4.3.6.1218

Qnap>>Qts >> Version 4.3.6.1263

Qnap>>Qts >> Version 4.3.6.1286

Qnap>>Qts >> Version 4.3.6.1333

Qnap>>Qts >> Version 4.3.6.1411

Qnap>>Qts >> Version 4.3.6.1446

Qnap>>Qts >> Version 4.5.1

Qnap>>Qts >> Version 4.5.1.1456

Qnap>>Qts >> Version 4.5.1.1461

Qnap>>Qts >> Version 4.5.1.1465

Qnap>>Qts >> Version 4.5.1.1480

Qnap>>Qts >> Version 4.5.2

Qnap>>Quts_hero >> Version To (excluding) h4.5.1

Qnap>>Quts_hero >> Version h4.5.1

Qnap>>Quts_hero >> Version h4.5.1.1472

References