# CVE-2012-0931: Missing authorization in n/a

> Remote attackers can execute arbitrary code or cause denial of service on Schneider Electric Modicon Quantum PLCs due to lack of authentication between Unity software and the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-348g-3f7x-jvgj

## What is CVE-2012-0931?

CVE-2012-0931 is a critical missing authorization vulnerability in n/a, published on 28 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Schneider Electric Modicon Quantum PLC does not perform authentication between the Unity software and PLC, which allows remote attackers to cause a denial of service or possibly execute arbitrary code via unspecified vectors.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Schneider-Electric Modicon Quantum Plc.

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

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

## Is CVE-2012-0931 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0929](https://insights.sbomify.com/CVE-2012-0929/): Memory corruption in n/a (high 7.5)
- [CVE-2012-0930](https://insights.sbomify.com/CVE-2012-0930/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0931 is a critical missing authorization vulnerability in n/a, published on 28 Jan 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-0931 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-0931/ (Markdown: https://insights.sbomify.com/CVE-2012-0931/index.md)
```

## Sources

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

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