# CVE-2011-3318: Denial of service in n/a

> Remote attackers can cause a denial of service on Cisco video surveillance cameras by sending crafted RTSP packets, requiring firmware upgrades to mitigate.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vj36-j2j5-pfw8

## What is CVE-2011-3318?

CVE-2011-3318 is a high-severity denial of service vulnerability in n/a, published on 27 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-399

## Which versions are affected by CVE-2011-3318?

It affects 4 products.


Products: Cisco Video Surveillance 2421, Cisco Video Surveillance 2500, Cisco Video Surveillance 2600, Cisco Video Surveillance Software.

## How do I fix CVE-2011-3318?

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

## Is CVE-2011-3318 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3318 and fix it if it is affected.

What it is: CVE-2011-3318 is a high-severity denial of service vulnerability in n/a, published on 27 Oct 2011. 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-2011-3318 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-2011-3318/ (Markdown: https://insights.sbomify.com/CVE-2011-3318/index.md)
```

## Sources

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

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