# CVE-2014-3293: Denial of service in n/a

> Remote attackers can cause denial of service on Cisco ASR901 devices by sending crafted IPv4 packets that trigger excessive CPU usage and BGP flapping.

- **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:** 28 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v734-5rx9-g3rm

## What is CVE-2014-3293?

CVE-2014-3293 is a medium-severity denial of service vulnerability in Cisco Ios, published on 28 Oct 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco IOS 15.4(3)S0b on ASR901 devices makes incorrect decisions to use the CPU for IPv4 packet processing, which allows remote attackers to cause a denial of service (BGP neighbor flapping) by sending many crafted IPv4 packets, aka Bug ID CSCuo29736.

Weakness: CWE-399

## Which versions are affected by CVE-2014-3293?

It affects 2 products.


Products: Cisco Asr901, Cisco Ios.

## How do I fix CVE-2014-3293?

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

## Is CVE-2014-3293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3293 and fix it if it is affected.

What it is: CVE-2014-3293 is a medium-severity denial of service vulnerability in Cisco Ios, published on 28 Oct 2014. 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-2014-3293 in the wild and no public exploit code.

Affected product: Cisco Ios. 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-2014-3293/ (Markdown: https://insights.sbomify.com/CVE-2014-3293/index.md)
```

## Sources

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

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