iobroker vulnerabilities
Recent CVEs affecting iobroker products. 3 tracked.
iobroker has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-11-25. Highest priority: CVE-2019-10765 (score 64/100).
- CVE-2019-10771 MEDIUM 6.1 UPGRADE Characters in the GET url path are not properly escaped and can be reflected in the server response.
- CVE-2019-10767 HIGH 7.5 UPGRADE An attacker can include file contents from outside the `/adapter/xxx/` directory, where `xxx` is the name of a
- CVE-2019-10765 CRITICAL 9.8 UPGRADE iobroker.admin before 3.6.12 allows attacker to include file contents from outside the `/log/file1/` directory
FAQ
How do I fix iobroker vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is iobroker being exploited right now?
None of the tracked iobroker CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which iobroker CVE should I patch first?
CVE-2019-10765 currently ranks highest (64/100): iobroker.admin before 3.6.12 allows attacker to include file contents from outside the `/log/file1/` directory.