CVE-2025-20184 : 상세 정보

CVE-2025-20184

7.2
/
높음
0.08%V4
2025-02-05
16h14 +00:00
Command Injection
A03-Injection
Network
2025-02-05
17h00 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

Cisco Secure Email and Web Manager and Secure Web Appliance Command Injection Vulnerability

A vulnerability in the web-based management interface of Cisco AsyncOS Software for Cisco Secure Email Gateway and Cisco Secure Web Appliance could allow an authenticated, remote attacker to perform command injection attacks against an affected device. The attacker must authenticate with valid administrator credentials. This vulnerability is due to insufficient validation of XML configuration files by an affected device. An attacker could exploit this vulnerability by uploading a crafted XML configuration file. A successful exploit could allow the attacker to inject commands to the underlying operating system with root privileges.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-20 Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-77 Improper Neutralization of Special Elements used in a Command
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.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 6.5 MEDIUM CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

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.

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.

V3.1 7.2 HIGH CVSS:3.1/AV:N/AC:L/PR:H/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.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

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

EPSS

EPSS는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.

EPSS 점수

EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.

EPSS 백분위수

백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.

언급된 제품

구성 0

Cisco>>Asyncos >> Version 13.0.0-392

Cisco>>Asyncos >> Version 13.0.5-007

Cisco>>Asyncos >> Version 13.5.1-277

Cisco>>Asyncos >> Version 13.5.4-038

Cisco>>Asyncos >> Version 14.0.0-698

Cisco>>Asyncos >> Version 14.2.0-620

Cisco>>Asyncos >> Version 14.2.1-020

Cisco>>Asyncos >> Version 14.3.0-032

Cisco>>Asyncos >> Version 15.0.0-104

Cisco>>Asyncos >> Version 15.0.1-030

Cisco>>Asyncos >> Version 15.0.3-002

Cisco>>Asyncos >> Version 15.5.0-048

Cisco>>Asyncos >> Version 15.5.1-055

Cisco>>Asyncos >> Version 15.5.2-018

Cisco>>Asyncos >> Version 15.5.3-022

Cisco>>Secure_email_gateway_virtual_appliance_c100v >> Version -

Cisco>>Secure_email_gateway_virtual_appliance_c300v >> Version -

Cisco>>Secure_email_gateway_virtual_appliance_c600v >> Version -

Cisco>>Secure_email_gateway_c195 >> Version -

Cisco>>Secure_email_gateway_c395 >> Version -

Cisco>>Secure_email_gateway_c695 >> Version -

구성 0

Cisco>>Asyncos >> Version 11.8.0-414

Cisco>>Asyncos >> Version 11.8.0-429

Cisco>>Asyncos >> Version 11.8.0-453

Cisco>>Asyncos >> Version 11.8.1-023

Cisco>>Asyncos >> Version 11.8.3-018

Cisco>>Asyncos >> Version 11.8.3-021

Cisco>>Asyncos >> Version 11.8.4-004

Cisco>>Asyncos >> Version 12.0.1-268

Cisco>>Asyncos >> Version 12.0.1-334

Cisco>>Asyncos >> Version 12.0.2-004

Cisco>>Asyncos >> Version 12.0.2-012

Cisco>>Asyncos >> Version 12.0.3-005

Cisco>>Asyncos >> Version 12.0.3-007

Cisco>>Asyncos >> Version 12.0.4-002

Cisco>>Asyncos >> Version 12.0.5-011

Cisco>>Asyncos >> Version 12.5.1-011

Cisco>>Asyncos >> Version 12.5.1-043

Cisco>>Asyncos >> Version 12.5.2-007

Cisco>>Asyncos >> Version 12.5.2-011

Cisco>>Asyncos >> Version 12.5.3-002

Cisco>>Asyncos >> Version 12.5.4-005

Cisco>>Asyncos >> Version 12.5.4-011

Cisco>>Asyncos >> Version 12.5.5-004

Cisco>>Asyncos >> Version 12.5.5-005

Cisco>>Asyncos >> Version 12.5.5-008

Cisco>>Asyncos >> Version 12.5.6-008

Cisco>>Asyncos >> Version 14.0.1-014

Cisco>>Asyncos >> Version 14.0.1-040

Cisco>>Asyncos >> Version 14.0.1-053

Cisco>>Asyncos >> Version 14.0.1-503

Cisco>>Asyncos >> Version 14.0.2-012

Cisco>>Asyncos >> Version 14.0.3-014

Cisco>>Asyncos >> Version 14.0.4-005

Cisco>>Asyncos >> Version 14.0.5-007

Cisco>>Asyncos >> Version 14.1.0-032

Cisco>>Asyncos >> Version 14.1.0-041

Cisco>>Asyncos >> Version 14.1.0-047

Cisco>>Asyncos >> Version 14.5.0-498

Cisco>>Asyncos >> Version 14.5.0-537

Cisco>>Asyncos >> Version 14.5.0-673

Cisco>>Asyncos >> Version 14.5.1-008

Cisco>>Asyncos >> Version 14.5.1-016

Cisco>>Asyncos >> Version 14.5.1-510

Cisco>>Asyncos >> Version 14.5.1-607

Cisco>>Asyncos >> Version 14.5.2-011

Cisco>>Asyncos >> Version 14.5.3-033

Cisco>>Asyncos >> Version 15.0.0-322

Cisco>>Asyncos >> Version 15.0.0-355

Cisco>>Asyncos >> Version 15.0.1-004

Cisco>>Asyncos >> Version 15.1.0-287

Cisco>>Asyncos >> Version 15.2.0-116

Cisco>>Asyncos >> Version 15.2.0-164

Cisco>>Asyncos >> Version 15.2.1-011

Cisco>>Secure_web_appliance_virtual_s1000v >> Version -

Cisco>>Secure_web_appliance_virtual_s100v >> Version -

Cisco>>Secure_web_appliance_virtual_s300v >> Version -

Cisco>>Secure_web_appliance_virtual_s600v >> Version -

Cisco>>Secure_web_appliance_s196 >> Version -

Cisco>>Secure_web_appliance_s396 >> Version -

Cisco>>Secure_web_appliance_s696 >> Version -

참고 자료