# CVE-2013-6949: Other in n/a

> Remote attackers can hijack connections in Belkin WeMo devices by exploiting improper STUN/TURN protocol usage, requiring access to one device.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m5gm-p83p-6vg3

## What is CVE-2013-6949?

CVE-2013-6949 is a critical vulnerability in n/a, published on 22 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Belkin WeMo Home Automation firmware before 3949 does not properly use the STUN and TURN protocols, which allows remote attackers to hijack connections and possibly have unspecified other impact by leveraging access to a single WeMo device.

Weakness: CWE-264

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

It affects 1 product.


Products: Belkin Wemo Home Automation Firmware.

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

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

## Is CVE-2013-6949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6952](https://insights.sbomify.com/CVE-2013-6952/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2013-6948](https://insights.sbomify.com/CVE-2013-6948/): XML external entity in n/a (high 7.8)
- [CVE-2013-6950](https://insights.sbomify.com/CVE-2013-6950/): Weak cryptography in n/a (high 7.8)
- [CVE-2013-6951](https://insights.sbomify.com/CVE-2013-6951/): Weak cryptography in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6949 is a critical vulnerability in n/a, published on 22 Feb 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6949 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-6949/ (Markdown: https://insights.sbomify.com/CVE-2013-6949/index.md)
```

## Sources

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

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