# CVE-2020-3506: Memory corruption in Cisco Video Surveillance 8000 Series IP Cameras

> Unauthenticated adjacent attackers can execute code or cause denial of service on Cisco Video Surveillance IP cameras via malicious CDP packets.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2020
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-39xx-m6h4-g776

## What is CVE-2020-3506?

CVE-2020-3506 is a high-severity memory corruption vulnerability in Cisco Video Surveillance 8000 Series IP Cameras, published on 26 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple vulnerabilities in the Cisco Discovery Protocol implementation for Cisco Video Surveillance 8000 Series IP Cameras could allow an unauthenticated, adjacent attacker to execute code remotely or cause a reload of an affected IP camera. These vulnerabilities are due to missing checks when the IP cameras process a Cisco Discovery Protocol packet. An attacker could exploit these vulnerabilities by sending a malicious Cisco Discovery Protocol packet to the targeted IP camera. A successful exploit could allow the attacker to execute code on the affected IP camera or cause it to reload unexpectedly, resulting in a denial of service (DoS) condition. Note: Cisco Discovery Protocol is a Layer 2 protocol. To exploit these vulnerabilities, an attacker must be in the same broadcast domain as the affected device (Layer 2 adjacent).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-3506?

It affects 8 products.


Products: Cisco 8000p Ip Camera Firmware, Cisco 8020 Ip Camera Firmware, Cisco 8030 Ip Camera Firmware, Cisco 8070 Ip Camera Firmware, Cisco 8400 Ip Camera Firmware, Cisco 8620 Ip Camera Firmware, Cisco 8630 Ip Camera Firmware, Cisco 8930 Speed Dome Ip Camera Firmware.

## How do I fix CVE-2020-3506?

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

## Is CVE-2020-3506 being exploited?

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

## Other vulnerabilities in Cisco Video Surveillance 8000 Series IP Cameras

- [CVE-2020-3544](https://insights.sbomify.com/CVE-2020-3544/): Memory corruption in Cisco Video Surveillance 8000 Series IP Cameras (high 8.8)
- [CVE-2020-3507](https://insights.sbomify.com/CVE-2020-3507/): Memory corruption in Cisco Video Surveillance 8000 Series IP Cameras (high 8.8)
- [CVE-2020-3543](https://insights.sbomify.com/CVE-2020-3543/): Cisco Video Surveillance 8000 Series IP Cameras Cisco Discovery Protocol Memory Leak Vulnerability (medium 6.5)
- [CVE-2020-3505](https://insights.sbomify.com/CVE-2020-3505/): Cisco Video Surveillance 8000 Series IP Cameras Cisco Discovery Protocol Memory Leak Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-3506 and fix it if it is affected.

What it is: CVE-2020-3506 is a high-severity memory corruption vulnerability in Cisco Video Surveillance 8000 Series IP Cameras, published on 26 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-3506 in the wild and no public exploit code.

Affected product: Cisco Video Surveillance 8000 Series IP Cameras. 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-2020-3506/ (Markdown: https://insights.sbomify.com/CVE-2020-3506/index.md)
```

## Sources

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

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