# CVE-2013-2572: Hardcoded credentials in n/a

> Hard-coded administrative credentials in TP-LINK IP cameras allow attackers to bypass authentication and access CGI files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 29 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fcmm-7862-g7xv

## What is CVE-2013-2572?

CVE-2013-2572 is a high-severity vulnerability in n/a, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Security Bypass vulnerability exists in TP-LINK IP Cameras TL-SC 3130, TL-SC 3130G, 3171G, 4171G, and 3130 1.6.18P12 due to default hard-coded credentials for the administrative Web interface, which could let a malicious user obtain unauthorized access to CGI files.

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

## Which versions are affected by CVE-2013-2572?

It affects 4 products.


Products: Tp-Link Tl-Sc 3130 Firmware, Tp-Link Tl-Sc 3130g Firmware, Tp-Link Tl-Sc 3171g Firmware, Tp-Link Tl-Sc 4171g Firmware.

## How do I fix CVE-2013-2572?

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

## Is CVE-2013-2572 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2572 exists.

Public exploit code:

- TP-Link IP Cameras Firmware 1.6.18P12 - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2572 and fix it if it is affected.

What it is: CVE-2013-2572 is a high-severity vulnerability in n/a, published on 29 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2572 exists.

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-2013-2572/ (Markdown: https://insights.sbomify.com/CVE-2013-2572/index.md)
```

## Sources

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

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