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

> Hardcoded guest credentials in QNAP VioStor NVR and Surveillance Station Pro allow remote attackers to gain unauthorized web-server access.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 7 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4c9v-w245-3ch6

## What is CVE-2013-0142?

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

### Official description

QNAP VioStor NVR devices with firmware 4.0.3, and the Surveillance Station Pro component in QNAP NAS, have a hardcoded guest account, which allows remote attackers to obtain web-server login access via unspecified vectors.

Weakness: CWE-255

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

It affects 3 products.


Products: Qnap Nas, Qnap Surveillance Station Pro, Qnap Viostor Network Video Recorder.

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

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

## Is CVE-2013-0142 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0143](https://insights.sbomify.com/CVE-2013-0143/): Command injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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