# CVE-2018-1000625: Hardcoded credentials in n/a

> Hard-coded administrative credentials in Battelle V2I Hub allow attackers to gain unauthorized admin access to the system.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j3gq-75j7-7266

## What is CVE-2018-1000625?

CVE-2018-1000625 is a critical vulnerability in n/a, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 any installation and gain unauthorized access to the system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2018-1000625?

It affects 1 product.


Products: Battelle V2i Hub.

## How do I fix CVE-2018-1000625?

No fix has been published for CVE-2018-1000625 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1000625 being exploited?

There is no known exploitation of CVE-2018-1000625 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-1000626](https://insights.sbomify.com/CVE-2018-1000626/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-1000627](https://insights.sbomify.com/CVE-2018-1000627/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-1000628](https://insights.sbomify.com/CVE-2018-1000628/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-1000631](https://insights.sbomify.com/CVE-2018-1000631/): SQL injection in n/a (critical 9.8)
- [CVE-2018-1000624](https://insights.sbomify.com/CVE-2018-1000624/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000625 and fix it if it is affected.

What it is: CVE-2018-1000625 is a critical vulnerability in n/a, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000625 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000625/ (Markdown: https://insights.sbomify.com/CVE-2018-1000625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000625
- OSV: https://osv.dev/vulnerability/CVE-2018-1000625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000625/
Summaries are generated and may contain mistakes; the official description above is the record.