# CVE-2013-1601: Information disclosure in n/a

> Attackers can access sensitive information from D-Link IP cameras via the lums.cgi script without authentication.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 28 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mhq4-hrhr-7vpg

## What is CVE-2013-1601?

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

### Official description

An Information Disclosure vulnerability exists due to a failure to restrict access on the lums.cgi script when processing a live video stream in D-LINK An Information Disclosure vulnerability exists due to a failure to restrict access on the lums.cgi script when processing a live video stream in D-LINK WCS-1100 1.02, TESCO DCS-2121 1.05_TESCO, TESCO DCS-2102 1.05_TESCO, DCS-7510 1.00, DCS-7410 1.00, DCS-6410 1.00, DCS-5635 1.01, DCS-5605 1.01, DCS-5230L 1.02, DCS-5230 1.02, DCS-3430 1.02, DCS-3411 1.02, DCS-3410 1.02, DCS-2121 1.06_FR, DCS-2121 1.06, DCS-2121 1.05_RU, DCS-2102 1.06_FR, DCS-2102 1.06, DCS-2102 1.05_RU, DCS-1130L 1.04, DCS-1130 1.04_US, DCS-1130 1.03, DCS-1100L 1.04, DCS-1100 1.04_US, and DCS-1100 1.03, which could let a malicious user obtain sensitive information. which could let a malicious user obtain sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 17 products.


Products: Dlink Dcs-1100 Firmware, Dlink Dcs-1100l Firmware, Dlink Dcs-1130 Firmware, Dlink Dcs-1130l Firmware, Dlink Dcs-2102 Firmware, Dlink Dcs-2121 Firmware, Dlink Dcs-3410 Firmware, Dlink Dcs-3411 Firmware, Dlink Dcs-3430 Firmware, Dlink Dcs-5230 Firmware, Dlink Dcs-5230l Firmware, Dlink Dcs-5605 Firmware, Dlink Dcs-5635 Firmware, Dlink Dcs-6410 Firmware, Dlink Dcs-7410 Firmware, Dlink Dcs-7510 Firmware, Dlink Wcs-1100 Firmware.

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

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

## Is CVE-2013-1601 being exploited?

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

Public exploit code:

- D-Link IP Cameras - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-1599](https://insights.sbomify.com/CVE-2013-1599/): Command injection in n/a (critical 9.8)
- [CVE-2017-8410](https://insights.sbomify.com/CVE-2017-8410/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8415](https://insights.sbomify.com/CVE-2017-8415/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8412](https://insights.sbomify.com/CVE-2017-8412/): Memory corruption in n/a (high 8.8)
- [CVE-2017-8413](https://insights.sbomify.com/CVE-2017-8413/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1601 is a medium-severity vulnerability in n/a, published on 28 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-1601 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-1601/ (Markdown: https://insights.sbomify.com/CVE-2013-1601/index.md)
```

## Sources

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

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