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

> Remote attackers can gain administrative access to ZTE routers via a hardcoded TELNET password derived from the MAC address.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cjwg-fm46-9qch

## What is CVE-2014-0329?

CVE-2014-0329 is a critical vulnerability in n/a, published on 4 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TELNET service on the ZTE ZXV10 W300 router 2.1.0 has a hardcoded password ending with airocon for the admin account, which allows remote attackers to obtain administrative access by leveraging knowledge of the MAC address characters present at the beginning of the password.

Weakness: CWE-255

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

It affects 1 product.


Products: Zte Zxv10 W300.

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

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

## Is CVE-2014-0329 being exploited?

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

Public exploit code:

- ZTE ZXV10 W300 Router - Hard-Coded Credentials (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-4018](https://insights.sbomify.com/CVE-2014-4018/): Hardcoded credentials in n/a (high 7.8)
- [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-0329 and fix it if it is affected.

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

## Sources

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

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