# CVE-2011-2010: Privilege escalation in n/a

> Local attackers can gain elevated privileges by exploiting improper access restrictions in the Microsoft Pinyin IME toolbar configuration options.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v9hv-xmm8-5vcw

## What is CVE-2011-2010?

CVE-2011-2010 is a high-severity vulnerability in n/a, published on 14 Dec 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Microsoft Office Input Method Editor (IME) for Simplified Chinese in Microsoft Pinyin IME 2010, Office Pinyin SimpleFast Style 2010, and Office Pinyin New Experience Style 2010 does not properly restrict access to configuration options, which allows local users to gain privileges via the Microsoft Pinyin (aka MSPY) IME toolbar, aka "Pinyin IME Elevation Vulnerability."

Weakness: CWE-264

## Which versions are affected by CVE-2011-2010?

It affects 3 products.


Products: Microsoft Pinyin Ime, Microsoft Pinyin New Experience Style, Microsoft Pinyin Simple Fast Style.

## How do I fix CVE-2011-2010?

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

## Is CVE-2011-2010 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2010 and fix it if it is affected.

What it is: CVE-2011-2010 is a high-severity vulnerability in n/a, published on 14 Dec 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-2010 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-2011-2010/ (Markdown: https://insights.sbomify.com/CVE-2011-2010/index.md)
```

## Sources

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

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