# CVE-2014-4018: Hardcoded credentials in n/a

> Remote attackers can gain administrative access to ZTE ZXV10 W300 routers using the default admin password.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8786-r836-vpr3

## What is CVE-2014-4018?

CVE-2014-4018 is a high-severity vulnerability in n/a, published on 16 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ZTE ZXV10 W300 router with firmware W300V1.0.0a_ZRD_LK has a default password of admin for the admin account, which makes it easier for remote attackers to obtain access via unspecified vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2014-4018?

It affects 2 products.


Products: Zte Zxv10 W300, Zte Zxv10 W300 Firmware.

## How do I fix CVE-2014-4018?

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

## Is CVE-2014-4018 being exploited?

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

Public exploit code:

- ZTE WXV10 W300 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-0329](https://insights.sbomify.com/CVE-2014-0329/): Hardcoded credentials in n/a (critical 9.3)
- [CVE-2014-4155](https://insights.sbomify.com/CVE-2014-4155/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-4154](https://insights.sbomify.com/CVE-2014-4154/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4018 and fix it if it is affected.

What it is: CVE-2014-4018 is a high-severity vulnerability in n/a, published on 16 Jul 2014. 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-2014-4018 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-2014-4018/ (Markdown: https://insights.sbomify.com/CVE-2014-4018/index.md)
```

## Sources

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

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