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

> Remote attackers can cause a serial-interface outage on Cisco 2900 devices via Frame Relay traffic when specific TDM/HDLC configurations are active.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 23 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2534-vvmm-cq7j

## What is CVE-2012-3918?

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

### Official description

Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

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

It affects 4 products.


Products: Cisco Catalyst 2900, Cisco Catalyst 2900 Vlan, Cisco Catalyst 2900xl, Cisco Ios.

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

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

## Is CVE-2012-3918 being exploited?

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

## Other vulnerabilities in Cisco Ios

- [CVE-2001-0566](https://insights.sbomify.com/CVE-2001-0566/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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