CVE-2012-3913
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 · uneditedThe Cisco VC220 and VC240 cameras allow remote attackers to cause a denial of service (WebUI outage) via crafted packets, aka Bug IDs CSCtf73188, CSCtf88059, CSCtf87951, CSCtf87908, and CSCtf88019.
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 · moderate confidenceThe Cisco VC220 and VC240 IP cameras contain a vulnerability where crafted network packets can cause the WebUI service to become unavailable, resulting in a denial of service condition. The issue affects the web interface component specifically and can be triggered remotely by attackers sending malicious packets to the device.
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 dataall versionsall versionsCVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the camera device modelAccess the camera's web interface login page, check the device label, or use network discovery tools (such as nmap or the camera's ONVIF/SSDP discovery) to retrieve the device model information. Look for model identifiers in the web UI footer or system information page.Affected if The device model is Cisco VC240 Network Bullet Camera or Cisco Video Surveillance Vc220 Network Dome Camera.
-
Confirm the device is a Cisco VC220 or VC240 modelCompare the identified model number against the affected product list. Verify the exact model string matches 'Vc240' or 'Vc220' (or variants like 'VC240', 'VC220').Affected if The model number matches Cisco VC240 or Cisco VC220 (any version).
-
Verify the WebUI service is enabledAttempt to access the camera's web interface by navigating to its IP address on ports 80 or 443. Check if the login page or authentication prompt loads.Affected if The WebUI is accessible and responds to HTTP/HTTPS requests, indicating the service is enabled.
-
Check current WebUI availabilitySend an HTTP request to the camera's IP address and observe the response. Use a tool like curl or a browser to test if the web interface returns a normal response or an error indicating unavailability.Affected if The WebUI fails to respond, returns an error, or exhibits intermittent availability, indicating a potential DoS condition.
If the device is a Cisco VC220 or VC240 camera with the WebUI service enabled, the environment is affected by this vulnerability since all versions of these models contain the flaw.
Generated from the published advisory. Verify against your own configuration.
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 dataOrganizations should update camera firmware to patched versions if available, implement network segmentation to limit exposure of camera management interfaces, and consider replacing end-of-life devices that no longer receive vendor support.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3913 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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