CVE-2023-47211 : Detail

CVE-2023-47211

9.1
/
Critical
Directory Traversal
A01-Broken Access Control
83.7%V4
Network
2024-01-08
14h45 +00:00
2024-08-02
21h01 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

A directory traversal vulnerability exists in the uploadMib functionality of ManageEngine OpManager 12.7.258. A specially crafted HTTP request can lead to arbitrary file creation. An attacker can send a malicious MiB file to trigger this vulnerability.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 9.1 CRITICAL CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

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.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

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.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.

Availability Impact

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

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

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.
V3.1 8.6 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

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.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

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.

None

There is no loss of confidentiality within the impacted component.

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.

None

There is no impact to availability within the impacted component.

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

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

Zohocorp>>Manageengine_firewall_analyzer >> Version To (excluding) 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_firewall_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version To (excluding) 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_netflow_analyzer >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version To (excluding) 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_network_configuration_manager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version To (excluding) 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version To (excluding) 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_msp >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version To (excluding) 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_opmanager_plus >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version To (excluding) 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

Zohocorp>>Manageengine_oputils >> Version 12.7

References