Battelle V2i Hub
8 CVEs affecting Battelle V2i Hub. Latest disclosed: 2018-12-28. Critical: 5, High: 2.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2018-1000631 | Critical | 9.8 | 2018-12-28 | Battelle V2I Hub 3.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements to the tmx/TmxCtl/src/lib/PluginStatus.cpp a… |
CVE-2018-1000628 | Critical | 9.8 | 2018-12-28 | Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the direct checking of the API key against a user-supplied valu… |
CVE-2018-1000627 | Critical | 9.8 | 2018-12-28 | Battelle V2I Hub 2.5.1 could allow a remote attacker to obtain sensitive information, caused by the failure to restrict access to the API key file. An attacker… |
CVE-2018-1000626 | Critical | 9.8 | 2018-12-28 | Battelle V2I Hub 2.5.1 could allow a remote attacker to bypass security restrictions, caused by the lack of requirement to change the default API key. An attac… |
CVE-2018-1000625 | Critical | 9.8 | 2018-12-28 | Battelle V2I Hub 2.5.1 contains hard-coded credentials for the administrative account. An attacker could exploit this vulnerability to log in as an admin on an… |
CVE-2018-1000624 | High | 7.5 | 2018-12-28 | Battelle V2I Hub 2.5.1 is vulnerable to a denial of service, caused by the failure to restrict access to a sensitive functionality. By visiting http://V2I_HUB/… |
CVE-2018-1000630 | High | 7.2 | 2018-12-28 | Battelle V2I Hub 2.5.1 is vulnerable to SQL injection. A remote authenticated attacker could send specially-crafted SQL statements to /api/PluginStatusActions… |
CVE-2018-1000629 | Medium | 6.1 | 2018-12-28 | Battelle V2I Hub 2.5.1 is vulnerable to cross-site scripting, caused by improper validation of user-supplied input by api/SystemConfigActions.php?action=add an… |