CVE-2011-1149

What it is

Android before 2.3 does not properly restrict access to the system property space, which allows local applications to bypass the application sandbox and gain privileges, as demonstrated by psneuter and KillingInTheNameOf, related to the use of Android shared memory (ashmem) and ASHMEM_SET_PROT_MASK.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2011-04-21 10:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:28 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 7.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2011-04-21 10:55 UTC

Last modified

2026-06-16 23:28 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Google Android ≤ 2.2.2
• Google Android 1.5
• Google Android 1.6
• Google Android 2.1
• Google Android 2.2
• Google Android 2.2.1

Attack profile CVSS 2.0 · 7.2

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2011-1149.md and follow it. Check whether this project is affected by CVE-2011-1149. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge