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

> Hardcoded credentials in TP-LINK IP camera firmware allow attackers to gain unauthorized access and potentially execute code.

- **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:** 30 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x3fm-5wpj-pq35

## What is CVE-2018-11482?

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

### Official description

/usr/lib/lua/luci/websys.lua on TP-LINK IPC TL-IPC223(P)-6, TL-IPC323K-D, TL-IPC325(KP)-*, and TL-IPC40A-4 devices has a hardcoded zMiVw8Kw0oxKXL0 password.

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

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

It affects 4 products.


Products: Tp-Link Ipc Tl-Ipc223\(p\)-6 Firmware, Tp-Link Tl-Ipc323k-D Firmware, Tp-Link Tl-Ipc325\(kp\) Firmware, Tp-Link Tl-Ipc40a-4 Firmware.

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

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

## Is CVE-2018-11482 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11481](https://insights.sbomify.com/CVE-2018-11481/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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