dbcve.org
Video Surveillance 2421Hardware / appliance · Cisco

CVE-2011-3318

HIGH · 7.8 CVSS v2.0 Published 2011-10-27
Fix available
A fix is available. Upgrade to after 4.2.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Cisco Video Surveillance 2421 and 2500 series cameras with software 1.1.x and 2.x before 2.4.0 and Video Surveillance 2600 series cameras with software before 4.2.0-13 allow remote attackers to cause a denial of service (device reload) by sending crafted RTSP packets over TCP, aka Bug IDs CSCtj96312, CSCtj39462, and CSCtl80175.

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

A denial of service vulnerability in Cisco Video Surveillance 2421, 2500, and 2600 series cameras allows remote attackers to crash/reload the devices by sending specially crafted RTSP packets over TCP. The vulnerability exists due to improper handling of RTSP traffic in the camera firmware versions prior to 2.4.0 (for 2421/2500) and 4.2.0-13 (for 2600 series).

MitigationApply the vendor-supplied firmware updates (2.4.0 or later for 2421/2500 series, 4.2.0-13 or later for 2600 series). If immediate patching is not possible, consider network segmentation to limit exposure to untrusted networks and blocking RTSP ports from external sources using firewall rules.

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
Video Surveillance 2421Hardware / appliance
Affected:all versions
Video Surveillance 2500Hardware / appliance
Affected:all versions
Video Surveillance SoftwareApplication
Affected:= 1.1.0= 1.2.1= 2.0.0= 2.1= 2.1.2= 2.1.3= 2.1.4= 2.1.6= 2.1.7= 2.3.0= 2.3.1<= 4.2.0
Video Surveillance 2600Hardware / appliance
Affected:all versions

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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/A:C

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's web interface, check the device label, or use SNMP/SSH to connect and run 'show version' or similar command to retrieve the model number (2421, 2500, or 2600)
    Affected if Model is Cisco Video Surveillance 2421, 2500, or 2600 series
  2. Determine the firmware version
    Log into the camera web interface (typically http://[camera-ip]), navigate to Administration or System settings, and locate the firmware version field. Alternatively, use CLI command 'show version' via SSH/Telnet
    Affected if Firmware version is below 2.4.0 for 2421/2500 series, or below 4.2.0-13 for 2600 series, or matches any of these versions: 1.1.0, 1.2.1, 2.0.0, 2.1, 2.1.2, 2.1.3, 2.1.4, 2.1.6, 2.1.7, 2.3.0, 2.3.1, or any version <= 4.2.0 for Video Surveillance Software
  3. Check if RTSP service is enabled
    Access camera settings via web interface or CLI. Look for RTSP settings under Network or Streaming configuration. Use 'show rtsp' or similar CLI command if available, or examine port 554 (default RTSP) listening status on the device
    Affected if RTSP streaming is enabled and accessible over TCP on the network

If the device is a 2421, 2500, or 2600 series camera running firmware prior to 2.4.0 (2421/2500) or 4.2.0-13 (2600), or running any of the listed affected software versions with RTSP enabled and reachable, the environment is vulnerable to CVE-2011-3318.

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
Upgrade available Upgrade to a release after 4.2.0
Interim mitigation

Apply the vendor-supplied firmware updates (2.4.0 or later for 2421/2500 series, 4.2.0-13 or later for 2600 series). If immediate patching is not possible, consider network segmentation to limit exposure to untrusted networks and blocking RTSP ports from external sources using firewall rules.

Fix this in Video Surveillance 2421 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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