dbcve.org
8000p Ip Camera FirmwareOperating system · Cisco

CVE-2020-3506

HIGH · 8.8 CVSS v3.1 Published 2020-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple vulnerabilities in the Cisco Discovery Protocol implementation for Cisco Video Surveillance 8000 Series IP Cameras allow an unauthenticated, adjacent attacker to execute code or cause device reload by sending malformed CDP packets. The vulnerabilities stem from missing input validation checks when processing CDP packets at Layer 2.

MitigationApply Cisco firmware updates for Video Surveillance 8000 Series IP Cameras when available; as immediate workaround, disable Cisco Discovery Protocol on affected devices or implement network segmentation to restrict Layer 2 access to trusted segments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
8000p Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8020 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8030 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8070 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8400 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8620 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8630 Ip Camera FirmwareOperating system
Affected:= 1.0.9-1
8930 Speed Dome Ip Camera FirmwareOperating system
Affected:= 1.0.9-1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the camera's web interface or use SNMP/CLI to query the hardware model. Common paths: web UI shows model under System > Device Info, or CLI command 'show version' returns model name like 'Cisco 8020 Ip Camera'.
    Affected if Device model is NOT one of: 8000p, 8020, 8030, 8070, 8400, 8620, 8630, 8930 Speed Dome.
  2. Check firmware version
    In the camera web UI, navigate to System > Firmware or System > Device Info to view the installed firmware version. Alternatively, use CLI command 'show version' or check via SNMP OID.
    Affected if Firmware version is exactly 1.0.9-1 (this is the only affected version listed).
  3. Verify CDP is enabled
    On the camera, go to Network > CDP (or Network Settings > Cisco Discovery Protocol) and check if CDP is enabled. From CLI, use 'show cdp neighbors' or check the CDP configuration with 'show run | include cdp'.
    Affected if Cisco Discovery Protocol is enabled (the vulnerability requires CDP to be processing packets).

Device is affected ONLY if it is one of the listed models (8000p, 8020, 8030, 8070, 8400, 8620, 8630, 8930), running firmware version 1.0.9-1, AND has CDP enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco firmware updates for Video Surveillance 8000 Series IP Cameras when available; as immediate workaround, disable Cisco Discovery Protocol on affected devices or implement network segmentation to restrict Layer 2 access to trusted segments.

Fix this in 8000p Ip Camera Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3506 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data