CVE-2011-4705
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Ming Blacklist Free (vc.software.blacklist) application 1.8.1 and 1.9.2.1 for Android does not properly protect data, which allows remote attackers to read or modify blacklists and a contact list via a crafted application that launches a "data-flow attack."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Ming Blacklist Free Android application versions 1.8.1 and 1.9.2.1 fails to properly protect its local data storage, allowing any other application installed on the same device to read or modify the blacklists and contact list through a data-flow attack. This indicates the app uses world-readable/writable storage or lacks proper Android sandboxing for its sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.8.1= 1.9.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify installed version of Ming Blacklist FreeCheck the application version through Android package manager (adb shell pm list packages -v com.ming.abc.blacklistfree or through device Settings > Apps > Ming Blacklist Free > Version)Affected if The installed version is exactly 1.8.1 or exactly 1.9.2.1
-
Confirm the application package nameVerify the package name is com.ming.abc.blacklistfree (or the specific package associated with Ming Blacklist Free) to ensure you are checking the correct vulnerable applicationAffected if The package name matches the vulnerable application and version is 1.8.1 or 1.9.2.1
-
Check data storage permissions (requires root or ADB)Use ADB to inspect file permissions in /data/data/com.ming.abc.blacklistfree/ - verify that files are NOT world-readable (should not have -rw-rw-rw permissions) and are protected by Android sandboxingAffected if Files in the app's data directory have world-readable (rwxrwxrwx or -rw-rw-rw-) permissions allowing any app to read/write the blacklist and contact data
A user is affected if Ming Blacklist Free version 1.8.1 or 1.9.2.1 is installed and the app's local storage uses insecure permissions that allow other applications to access the blacklist and contact list data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUsers should ensure only trusted applications are installed on the device and update to a patched version if available. The vendor must implement proper Android private storage (Context.MODE_PRIVATE) and enforce appropriate file permissions to prevent cross-application data access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-4705 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data