Ruckus Wireless Unleashed up to 200.7.10.102.64 Web Interface bin/web.conf HTTP Requests information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, was found in Ruckus Wireless Unleashed up to 200.7.10.102.64. This vulnerability affects unknown code of the file bin/web.conf of the component Web Interface. Executing a manipulation as part of HTTP Requests can lead to information disclosure. The identification of this vulnerability is CVE-2019-19837. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic was found in Ruckus Wireless Unleashed up to 200.7.10.102.64. This vulnerability affects some unknown functionality of the file bin/web.conf of the component Web Interface. The manipulation as part of a HTTP Requests leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:

Incorrect access control in the web interface in Ruckus Wireless Unleashed through 200.7.10.102.64 allows remote information disclosure of bin/web.conf via HTTP requests.

The weakness was shared 01/23/2020. This vulnerability was named CVE-2019-19837 since 12/17/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-149286, VDB-149285 and VDB-149283 are related to this item. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Ruckus Wireless

Name

• Unleashed

Version

• 200.7.10.102.0
• 200.7.10.102.1
• 200.7.10.102.2
• 200.7.10.102.3
• 200.7.10.102.4
• 200.7.10.102.5
• 200.7.10.102.6
• 200.7.10.102.7
• 200.7.10.102.8
• 200.7.10.102.9
• 200.7.10.102.10
• 200.7.10.102.11
• 200.7.10.102.12
• 200.7.10.102.13
• 200.7.10.102.14
• 200.7.10.102.15
• 200.7.10.102.16
• 200.7.10.102.17
• 200.7.10.102.18
• 200.7.10.102.19
• 200.7.10.102.20
• 200.7.10.102.21
• 200.7.10.102.22
• 200.7.10.102.23
• 200.7.10.102.24
• 200.7.10.102.25
• 200.7.10.102.26
• 200.7.10.102.27
• 200.7.10.102.28
• 200.7.10.102.29
• 200.7.10.102.30
• 200.7.10.102.31
• 200.7.10.102.32
• 200.7.10.102.33
• 200.7.10.102.34
• 200.7.10.102.35
• 200.7.10.102.36
• 200.7.10.102.37
• 200.7.10.102.38
• 200.7.10.102.39
• 200.7.10.102.40
• 200.7.10.102.41
• 200.7.10.102.42
• 200.7.10.102.43
• 200.7.10.102.44
• 200.7.10.102.45
• 200.7.10.102.46
• 200.7.10.102.47
• 200.7.10.102.48
• 200.7.10.102.49
• 200.7.10.102.50
• 200.7.10.102.51
• 200.7.10.102.52
• 200.7.10.102.53
• 200.7.10.102.54
• 200.7.10.102.55
• 200.7.10.102.56
• 200.7.10.102.57
• 200.7.10.102.58
• 200.7.10.102.59
• 200.7.10.102.60
• 200.7.10.102.61
• 200.7.10.102.62
• 200.7.10.102.63
• 200.7.10.102.64

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion