# CVE-2012-3913: Denial of service in n/a

> Remote attackers can cause a denial of service on Cisco VC220 and VC240 cameras by sending crafted packets to the WebUI.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g2xq-jpp7-4p9p

## What is CVE-2012-3913?

CVE-2012-3913 is a medium-severity denial of service vulnerability in n/a, published on 31 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

## Which versions are affected by CVE-2012-3913?

It affects 2 products.


Products: Cisco Vc240 Network Bullet Camera, Cisco Video Surveillance Vc220 Network Dome Camera.

## How do I fix CVE-2012-3913?

No fix has been published for CVE-2012-3913 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-3913 being exploited?

There is no known exploitation of CVE-2012-3913 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-3913 and fix it if it is affected.

What it is: CVE-2012-3913 is a medium-severity denial of service vulnerability in n/a, published on 31 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3913 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-3913/ (Markdown: https://insights.sbomify.com/CVE-2012-3913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-3913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-3913
- OSV: https://osv.dev/vulnerability/CVE-2012-3913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-3913/
Summaries are generated and may contain mistakes; the official description above is the record.