# CVE-2012-4249: Command injection in n/a

> Attackers can execute arbitrary commands on Kindle Touch devices via shell metacharacters in system event strings, requiring local or adjacent access.

- **Severity:** Critical 10.0 (`AV:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-32q7-jcv7-p935

## What is CVE-2012-4249?

CVE-2012-4249 is a critical command injection vulnerability in n/a, published on 12 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Amazon Lab126 com.lab126.system sendEvent implementation on the Kindle Touch before 5.1.2 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a string, as demonstrated by using lipc-set-prop to set an LIPC property, a different vulnerability than CVE-2012-4248.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Amazon Kindle Touch.

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

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

## Is CVE-2012-4249 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4248](https://insights.sbomify.com/CVE-2012-4248/): Missing authorization in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4249 is a critical command injection vulnerability in n/a, published on 12 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-4249 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-4249/ (Markdown: https://insights.sbomify.com/CVE-2012-4249/index.md)
```

## Sources

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

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