PatchTheCVEspidercontrol vulnerabilities
Recent CVEs affecting spidercontrol products. 7 tracked.
spidercontrol has 7 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 6. Most recent: 2023-08-02. Highest priority: CVE-2017-13995 (score 61/100).
- CVE-2023-3329 MEDIUM 6.5 UPGRADE SpiderControl SCADA Webserver versions 2.08 and prior are vulnerable to path traversal
- CVE-2018-18991 MEDIUM 6.1 UPGRADE Reflected cross-site scripting (non-persistent) in SCADA WebServer (Versions prior to 2.03.0001) could allow a
- CVE-2017-14010 HIGH 7.8 UPGRADE In SpiderControl MicroBrowser Windows XP, Vista 7, 8 and 10, Versions 1.6.30.144 and prior, an uncontrolled se
- CVE-2017-13995 CRITICAL 10.0 UPGRADE An Improper Authentication issue was discovered in iniNet Solutions iniNet Webserver, all versions prior to V2
- CVE-2017-12728 HIGH 7.8 UPGRADE An Improper Privilege Management issue was discovered in SpiderControl SCADA Web Server Version 2.02.0007 and
- CVE-2017-12707 CRITICAL 9.8 UPGRADE A Stack-based Buffer Overflow issue was discovered in SpiderControl SCADA MicroBrowser Versions 1.6.30.144 and
- CVE-2017-12694 HIGH 7.5 MITIGATE A Directory Traversal issue was discovered in SpiderControl SCADA Web Server
FAQ
How do I fix spidercontrol 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 spidercontrol being exploited right now?
None of the tracked spidercontrol CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which spidercontrol CVE should I patch first?
CVE-2017-13995 currently ranks highest (61/100): An Improper Authentication issue was discovered in iniNet Solutions iniNet Webserver, all versions prior to V2.