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

> Attackers can gain administrative access to iBall routers using hardcoded default passwords for admin, support, and user accounts.

- **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:** 29 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-376h-xh6m-wfrm

## What is CVE-2018-6387?

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

### Official description

iBall iB-WRA150N 1.2.6 build 110401 Rel.47776n devices have a hardcoded password of admin for the admin account, a hardcoded password of support for the support account, and a hardcoded password of user for the user account.

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

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

It affects 1 product.


Products: Iball Ib-Wra150n Firmware.

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

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

## Is CVE-2018-6387 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14244](https://insights.sbomify.com/CVE-2017-14244/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-6558](https://insights.sbomify.com/CVE-2017-6558/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-6388](https://insights.sbomify.com/CVE-2018-6388/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6387 is a critical vulnerability in n/a, published on 29 Jan 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-6387 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-6387/ (Markdown: https://insights.sbomify.com/CVE-2018-6387/index.md)
```

## Sources

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

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