CVE intelligence and bounded remediation

CVE-2020-3505 — Cisco 8000P Ip Camera Firmware security vulnerability

Medium CVSS 6.5

A vulnerability in the Cisco Discovery Protocol of Cisco Video Surveillance 8000 Series IP Cameras could allow an unauthenticated, adjacent attacker to cause a memory leak, which could lead to a denial of service (DoS) condition on an affected device. The vulnerability is due to incorrect processing of certain Cisco Discovery Protocol packets. An attacker could exploit this vulnerability by sending certain Cisco Discovery Protocol packets to an affected device. A successful exploit could allow the attacker to cause the affected device to continuously consume memory, which could cause the device to crash and reload, resulting in a DOS condition. Note: Cisco Discovery Protocol is a Layer 2 protocol. To exploit this vulnerability, an attacker must be in the same broadcast domain as the affected device (Layer 2 adjacent).

Severity
Medium
CVSS
6.5 (3.1)
Published
2020-08-26
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-400, CWE-401

Affected products

  • cisco / 8000p_ip_camera_firmware / 1.0.9-1
  • cisco / 8020_ip_camera_firmware / 1.0.9-1
  • cisco / 8030_ip_camera_firmware / 1.0.9-1
  • cisco / 8070_ip_camera_firmware / 1.0.9-1
  • cisco / 8400_ip_camera_firmware / 1.0.9-1
  • cisco / 8620_ip_camera_firmware / 1.0.9-1

Showing 6 representative product identities from 8 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Resource exhaustion and denial of service

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify attacker-influenced work factors including input size, nesting, compression, fan-out, regex cost, allocation, recursion, retries, and connection lifetime.
  • Map per-request and shared CPU, memory, disk, descriptor, thread, queue, and downstream-service limits.
  • Determine whether authentication, tenancy, quotas, and rate controls apply before expensive processing begins.

Remediate safely

  • Bound input size, nesting, expansion, work, concurrency, queue depth, retries, and execution time before resource-intensive processing.
  • Release resources on every success, error, cancellation, and timeout path and use backpressure instead of unbounded buffering.
  • Update affected components and add small deterministic tests that assert resource ceilings rather than exhausting a host.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.