CVE-2018-1000627: Battelle V2I Hub 2.5.1 could allow a remote attacker to obtain sensitive information, caused by the failure to

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2018-1000627 is a critical-severity flaw (CVSS 9.8) affecting v2i hub. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 could exploit this vulnerability to obtain the current API key to gain unauthorized access to the system.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-522
Published	2018-12-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: battelle

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-12-28 16:29 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

battelle v2i hub DOWNGRADE

Affected: 2.5.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.5.1

1. Check installed version

apt-cache policy v2i-hub || rpm -q v2i-hub || v2i-hub --version

2. No fixed release: DOWNGRADE to a release before 2.5.1 (Debian / Ubuntu)

apt-cache madison v2i-hub sudo apt install v2i-hub=<VERSION_BEFORE_2.5.1> sudo apt-mark hold v2i-hub

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list v2i-hub sudo dnf downgrade v2i-hub-<VERSION_BEFORE_2.5.1> sudo dnf versionlock add v2i-hub

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1000627?

v2i hub: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-1000627 being exploited?

CVE-2018-1000627 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1000627 affect?

CVE-2018-1000627 affects v2i hub. Severity is critical (CVSS 9.8). 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 could exploit this vulnerability to obtain the current API key to gain unauthori

How urgent is CVE-2018-1000627?

Priority 60/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

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-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

References

← Back to latest CVEs