CVE-2019-10771: Cross-Site Scripting in iobroker.web
Summary
CVE-2019-10771: Cross-Site Scripting in iobroker.web. Affects iobroker.web versions < 2.4.10. Fixed in 2.4.10. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The iobroker.web package is an npm package that provides a web interface for the iobroker home automation platform. It allows users to control and monitor their smart home devices through a web browser. The package is widely used and has a moderate severity vulnerability that can lead to Cross-Site Scripting (XSS) attacks.
Vulnerability Detail
Versions of iobroker.web prior to 2.4.10 are vulnerable to Cross-Site Scripting. The package fails to escape URL parameters that may be reflected in the server response. This can be exploited by attackers to execute arbitrary JavaScript code in the victim's browser. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level. If exploited, it can lead to unauthorized access, data theft, and potential compromise of the user's smart home devices.
How To Fix
Minimum fixed version
2.4.10
This is the first release that contains the fix.
npm install iobroker.web@2.4.10Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The iobroker.web package prior to version 2.4.10 is vulnerable to Cross-Site Scripting (XSS) attacks. It is crucial to upgrade to the latest version to ensure the security of the web interface and protect against potential exploits. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for iobroker.web →
FAQ
The vulnerability allows attackers to execute arbitrary JavaScript code in the victim's browser, potentially leading to unauthorized access, data theft, and compromise of smart home devices.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will provide real-time alerts for open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is recommended to upgrade to the latest version of the iobroker.web package to mitigate the risk.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to promptly update the package to the latest version to prevent any potential attacks.
This vulnerability was discovered and reported by the GitHub Security Lab. The details and fix for the vulnerability can be found in the GitHub Advisory Database.
