PatchTheCVEv2i hub vulnerabilities and fixes
Recent CVEs affecting v2i hub, with upgrade or downgrade steps. 8 tracked.
Also searched as: v2ihub.
v2i hub has 8 tracked vulnerabilities, 5 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-12-28. Highest priority: CVE-2018-1000628 (score 61/100).
- CVE-2018-1000631 CRITICAL 9.8 DOWNGRADE Battelle V2I Hub 3.0 is vulnerable to SQL injection
- CVE-2018-1000630 HIGH 7.2 DOWNGRADE Battelle V2I Hub 2.5.1 is vulnerable to SQL injection
- CVE-2018-1000629 MEDIUM 6.1 DOWNGRADE Battelle V2I Hub 2.5.1 is vulnerable to cross-site scripting, caused by improper validation of user-supplied i
- CVE-2018-1000628 CRITICAL 9.8 DOWNGRADE Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the direct che
- CVE-2018-1000627 CRITICAL 9.8 DOWNGRADE Battelle V2I Hub 2.5.1 could allow a remote attacker to obtain sensitive information, caused by the failure to
- CVE-2018-1000626 CRITICAL 9.8 DOWNGRADE Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the lack of re
- CVE-2018-1000625 CRITICAL 9.8 DOWNGRADE Battelle V2I Hub 2.5.1 contains hard-coded credentials for the administrative account
- CVE-2018-1000624 HIGH 7.5 DOWNGRADE Battelle V2I Hub 2.5.1 is vulnerable to a denial of service, caused by the failure to restrict access to a sen
FAQ
How do I fix v2i hub 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 v2i hub being exploited right now?
None of the tracked v2i hub CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which v2i hub CVE should I patch first?
CVE-2018-1000628 currently ranks highest (61/100): Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the direct che.