CVE-2011-4769
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 360 MobileSafe (com.qihoo360.mobilesafe) application 2.x before 2.3.0 for Android does not properly protect data, which allows remote attackers to read or modify SMS messages and a contact list 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 360 MobileSafe Android application versions prior to 2.3.0 fails to properly protect sensitive data stored on the device. This improper data protection allows any malicious application installed on the same Android device to read or modify SMS messages and the user's contact list, exploiting insufficient access controls or insecure data storage mechanisms.
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= 2.1.0= 2.2.0CVSS 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.
-
Check if 360 MobileSafe is installedOpen the device Settings, navigate to Applications or Apps, and look for '360 MobileSafe' or '360 Mobilesafe' in the list of installed applications.Affected if The application is present on the device
-
Determine the installed versionIn Settings > Applications > 360 MobileSafe, locate the version information typically displayed as 'Version' or 'Version name' under the app details.Affected if The version shown is 2.1.0 or 2.2.0 exactly
-
Verify SMS permission is grantedIn Settings > Applications > 360 MobileSafe > Permissions, inspect whether the SMS or Messages permission is enabled or granted.Affected if SMS permission is granted and the installed version is 2.1.0 or 2.2.0
-
Verify Contacts permission is grantedIn Settings > Applications > 360 MobileSafe > Permissions, inspect whether the Contacts or Contacts read permission is enabled or granted.Affected if Contacts permission is granted and the installed version is 2.1.0 or 2.2.0
A user is affected if 360 MobileSafe version 2.1.0 or 2.2.0 is installed and the app has SMS or Contacts permissions enabled, allowing any other app on the device to access that 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 dataUpgrade to version 2.3.0 or later which includes proper data protection mechanisms. Until then, avoid installing untrusted applications on devices with this app installed, as a crafted malicious app can access the vulnerable application's data.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4769 — 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-4769 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