CVE-2011-4698
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 AndroidAppTools Easy Filter (com.phoneblocker.android) application 1.1 and 1.2 for Android does not properly protect data, which allows remote attackers to read or modify SMS messages and call records via a crafted application.
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 AndroidAppTools Easy Filter application for Android versions 1.1 and 1.2 fails to properly protect sensitive data, specifically SMS messages and call records. This improper data protection allows a malicious application installed on the same device to read or modify this sensitive communication data without proper authorization.
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.1= 1.2CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/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 Easy Filter app is installedOpen Android Settings > Apps > Apps and look for 'Easy Filter' or 'AndroidAppTools Easy Filter' in the installed applications listAffected if The application is present on the device and the vulnerability can potentially be exploited
-
Check the installed version numberTap on the Easy Filter app in Settings > Apps, then look at the 'Version' or 'Version info' field under App infoAffected if The version displayed is exactly 1.1 or exactly 1.2, matching the affected versions in the CVE
-
Verify app permissions include SMS and call log accessIn Settings > Apps > Easy Filter > Permissions, check if permissions for 'SMS' and 'Call log' or 'Phone' are grantedAffected if These sensitive permissions are granted to the app, which is required for the improper data protection flaw to be exploitable
-
Confirm other applications can access deviceCheck that other applications are installed on the same device, which could potentially exploit the data protection weaknessAffected if Other applications exist on the device alongside Easy Filter, providing a potential attack vector for unauthorized data access
You are affected if the AndroidAppTools Easy Filter version 1.1 or 1.2 is installed on your Android device and has SMS/call log permissions enabled.
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 dataRemediate by implementing proper Android permission controls, using encrypted storage mechanisms (such as Android's EncryptedSharedPreferences), and securing inter-component communication to prevent unauthorized access to SMS and call log data.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4698 — 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-4698 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