Affected Systems
Discovered By
Vulnerability Details
Vulnerability Description
API keys for CommScope Ruckus are included in the IoT Controller OVA image, and are exposed to attackers who mount the filesystem.
Technical Description
Ruckus vRIoT server software is available from the software library at: https://support.ruckuswireless.com/software/
Once the OVA is imported into VirtualBox, a VMDK file is created. The VMDK file can be mounted and the directory structure and its contents can be perused. The virtual appliance contains clear text API keys that are hard-coded into the web application code. The API keys can be abused to gain information about deployed assets and send email via SendGrid as Commscope/Ruckus. While the AWS SECRET_KEY is exposed, an ACCESS_KEY is not.
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
With the VMDK file mounted at the current working directory:
root@vriot:/# grep -R 'KIO_API_KEY' /VRIOT/ 2>/dev/null
./VRIOT/backend/settings/defaults.py:KIO_API_KEY = os.environ.get("KIO_API_KEY", "wxtPbzgNNWFlfBqhDfEDoZkQUxtnhWTq")
$ egrep -r 'SECRET_KEY|ACCESS_KEY' ./VRIOT/*
./VRIOT/authServer/app/baseapp/settings.py:SECRET_KEY = 'db$04-yk#-3&=54s78d-tvu!+e3#621kj9s!3g$x3t^@m1m6#i'
./VRIOT/backend/settings/settings.py:SECRET_KEY = '%u9-#a6eo0!ukif-+kcg3=gc-zlh8o3@)rz@!-74(g*xa0c#bb'
Binary file ./VRIOT/backend/lora/lorawan1.6.0.0.tar matches
Binary file ./VRIOT/ops/scripts/image_push.pyc matches
./VRIOT/ops/sqlite_modules/aws4/README.md:// or it can get credentials from process.env.AWS_ACCESS_KEY_ID, etc
./VRIOT/ops/sqlite_modules/aws4/README.md:export AWS_ACCESS_KEY_ID="<your-access-key-id>"
./VRIOT/ops/sqlite_modules/aws4/README.md:export AWS_SECRET_ACCESS_KEY="<your-secret-access-key>"
./VRIOT/ops/sqlite_modules/aws4/README.md:(will also use `AWS_ACCESS_KEY` and `AWS_SECRET_KEY` if available)
./VRIOT/ops/sqlite_modules/aws4/aws4.js: accessKeyId: env.AWS_ACCESS_KEY_ID || env.AWS_ACCESS_KEY,
./VRIOT/ops/sqlite_modules/aws4/aws4.js: secretAccessKey: env.AWS_SECRET_ACCESS_KEY || env.AWS_SECRET_KEY,$ more ./VRIOT/authServer# more app/baseapp/settings.py
...
# Email server settings.
EMAIL_HOST = 'smtp.sendgrid.net'
EMAIL_HOST_USER = 'apikey'
EMAIL_HOST_PASSWORD = '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'
EMAIL_PORT = 587
EMAIL_USE_TLS = True
...Per https://sendgrid.com/docs/API_Reference/SMTP_API/integrating_with_the_smtp_api.html, the SendGrid password identified above is actually an API key, which can be used with the ‘apikey’ user to send email through the SendGrid platform as Commscope Ruckus.
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-33220.
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.