# CVE-2013-7487: Command injection in n/a

> Remote attackers can execute arbitrary code on Swann DVR devices via a command injection vulnerability in the raysharpdvr application.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 21 Mar 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h44x-3xxx-8jpc

## What is CVE-2013-7487?

CVE-2013-7487 is a critical command injection vulnerability in n/a, published on 21 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Swann DVR04B, DVR08B, DVR-16CIF, and DVR16B devices, raysharpdvr application has a vulnerable call to “system”, which allows remote attackers to execute arbitrary code via TCP port 9000.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 4 products.


Products: Swann Dvr-16cif Firmware, Swann Dvr04b Firmware, Swann Dvr08b Firmware, Swann Dvr16b Firmware.

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

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

## Is CVE-2013-7487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7487 is a critical command injection vulnerability in n/a, published on 21 Mar 2020. 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-7487 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-7487/ (Markdown: https://insights.sbomify.com/CVE-2013-7487/index.md)
```

## Sources

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

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