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

> Remote attackers can cause a denial of service on Cisco MDS switches by sending a crafted FCIP header, requiring a module reload.

- **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:** 6 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r2wv-4x27-jjx6

## What is CVE-2012-1340?

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

### Official description

The Fibre Channel over IP (FCIP) implementation in Cisco MDS NX-OS 4.2 and 5.2 on MDS 9000 series switches allows remote attackers to cause a denial of service (module reload) via a crafted FCIP header, aka Bug ID CSCtn93151.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Cisco Mds 9000 Nx-Os.

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

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

## Is CVE-2012-1340 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6655](https://insights.sbomify.com/CVE-2017-6655/): Denial of service in Cisco NX-OS Software Fibre Channel over Ethernet (medium 6.5)
- [CVE-2015-4323](https://insights.sbomify.com/CVE-2015-4323/): Memory corruption in n/a (medium 6.1)
- [CVE-2015-0775](https://insights.sbomify.com/CVE-2015-0775/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1340 is a medium-severity denial of service vulnerability in n/a, published on 6 Aug 2012. 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-1340 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-1340/ (Markdown: https://insights.sbomify.com/CVE-2012-1340/index.md)
```

## Sources

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

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