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

> Remote attackers can cause denial of service on Allen-Bradley controllers by triggering status bit modifications when Static status is disabled.

- **Severity:** High 7.1 (`AV:N/AC:M/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:** 8 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mqxm-crwg-978x

## What is CVE-2012-4690?

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

### Official description

Rockwell Automation Allen-Bradley MicroLogix controller 1100, 1200, 1400, and 1500; SLC 500 controller platform; and PLC-5 controller platform, when Static status is not enabled, allow remote attackers to cause a denial of service via messages that trigger modification of status bits.

Weakness: CWE-16

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

It affects 3 products.


Products: Rockwellautomation Ab Micrologix Controller, Rockwellautomation Plc-5 Controller, Rockwellautomation Slc 500 Controller.

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

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

## Is CVE-2012-4690 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5410](https://insights.sbomify.com/CVE-2014-5410/): Rockwell Automation Micrologix 1400 Improper Input Validation (high 7.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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