# CVE-2013-1595: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a buffer overflow in the RTSP service of Vivotek IP cameras.

- **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:** 24 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9232-vjr9-4mqp

## What is CVE-2013-1595?

CVE-2013-1595 is a critical memory corruption vulnerability in n/a, published on 24 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Buffer Overflow vulnerability exists in Vivotek PT7135 IP Camera 0300a and 0400a via a specially crafted packet in the Authorization header field sent to the RTSP service, which could let a remote malicious user execute arbitrary code or cause a Denial of Service.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Vivotek Pt7135 Firmware.

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

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

## Is CVE-2013-1595 being exploited?

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

Public exploit code:

- Vivotek IP Cameras - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-1598](https://insights.sbomify.com/CVE-2013-1598/): Command injection in n/a (high 8.8)
- [CVE-2013-1594](https://insights.sbomify.com/CVE-2013-1594/): Information disclosure in n/a (high 7.5)
- [CVE-2013-1597](https://insights.sbomify.com/CVE-2013-1597/): Path traversal in n/a (medium 6.5)
- [CVE-2013-1596](https://insights.sbomify.com/CVE-2013-1596/): Auth bypass in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1595 is a critical memory corruption vulnerability in n/a, published on 24 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-1595 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-1595/ (Markdown: https://insights.sbomify.com/CVE-2013-1595/index.md)
```

## Sources

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

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