# CVE-2013-4985: Auth bypass in n/a

> Attackers can bypass authentication to access video streams on Vivotek IP cameras, compromising privacy and security.

- **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:** 27 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6mrp-w3p5-m293

## What is CVE-2013-4985?

CVE-2013-4985 is a high-severity authentication bypass vulnerability in n/a, published on 27 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple Vivotek IP Cameras remote authentication bypass that could allow access to the video stream

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 3 products.


Products: Vivotek Ip7160 Firmware, Vivotek Ip7361 Firmware, Vivotek Ip8332 Firmware.

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

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

## Is CVE-2013-4985 being exploited?

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

Public exploit code:

- Vivotek IP Cameras - RTSP Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4985 is a high-severity authentication bypass vulnerability in n/a, published on 27 Dec 2019. 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-4985 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-4985/ (Markdown: https://insights.sbomify.com/CVE-2013-4985/index.md)
```

## Sources

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

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