dbcve.org
8000p Ip Camera FirmwareOperating system · Cisco

CVE-2020-3543

MEDIUM · 6.5 CVSS v3.1 Published 2020-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
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).

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

Memory leak vulnerability in Cisco Discovery Protocol (CDP) on Video Surveillance 8000 Series IP Cameras. An unauthenticated adjacent attacker (Layer 2 same broadcast domain) sends specially crafted CDP packets that cause improper memory handling, leading to continuous memory consumption and eventual device crash/reboot.

MitigationDisable Cisco Discovery Protocol on affected cameras if not required for legitimate operations; otherwise apply Cisco firmware updates when available and enforce Layer 2 network segmentation to restrict adjacent attackers.

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-4
8020 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8030 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8070 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8400 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8620 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8630 Ip Camera FirmwareOperating system
Affected:= 1.0.9-4
8930 Speed Dome Ip Camera FirmwareOperating system
Affected:= 1.0.9-4

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the camera model
    Access the camera web interface or check the physical device label to determine the exact model number. Compare against the affected models: 8000p, 8020, 8030, 8070, 8400, 8620, 8630, or 8930 Speed Dome.
    Affected if The camera model is one of these eight models.
  2. Check the firmware version
    Log into the camera administrative interface and navigate to the system information or firmware version page. Alternatively, use the camera's API or command-line interface if available to retrieve the installed firmware version.
    Affected if The firmware version is exactly 1.0.9-4.
  3. Verify if CDP is enabled
    Access the camera network settings through the web interface or CLI and check the Cisco Discovery Protocol status. This is typically found under network protocol settings, interface configuration, or discovery settings.
    Affected if CDP is enabled and running on the device.
  4. Confirm network exposure
    Review network topology and VLAN configuration to determine if the camera is on the same Layer 2 broadcast domain as untrusted or attacker-controlled devices.
    Affected if The camera is accessible to adjacent attackers on the same broadcast domain.

A user is affected if they have one of the eight listed camera models running firmware version 1.0.9-4 with CDP enabled and exposed to adjacent network attackers.

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

Disable Cisco Discovery Protocol on affected cameras if not required for legitimate operations; otherwise apply Cisco firmware updates when available and enforce Layer 2 network segmentation to restrict adjacent attackers.

Fix this in 8000p Ip Camera Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3543 — 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-3543 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