CVE-2011-4772
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 KouXin (com.qihoo360.kouxin) application 1.5.3 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 KouXin (com.qihoo360.kouxin) Android application version 1.5.3 does not properly protect sensitive data, allowing malicious applications on the same device to read or modify SMS messages and the contact list due to inadequate data encryption or insecure storage/permission handling.
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.5.3CVSS 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 KouXin is installedOpen Android Settings > Apps > look for 360 KouXin or KouXin in the app list, or use ADB command: adb shell pm list packages | grep qihoo360Affected if The package com.qihoo360.kouxin appears in the installed packages
-
Verify the installed version is 1.5.3In Settings > Apps > 360 KouXin, check the version number under App Info, or use ADB: adb shell dumpsys package com.qihoo360.kouxin | grep versionNameAffected if The version displayed is exactly 1.5.3
-
Check if SMS permissions are grantedIn Settings > Apps > 360 KouXin > Permissions, verify if the app has SMS or Messages permission, or use ADB: adb shell dumpsys package com.qihoo360.kouxin | grep -i smsAffected if The app holds SMS-related permissions (READ_SMS, WRITE_SMS, RECEIVE_SMS)
-
Check if contacts permissions are grantedIn Settings > Apps > 360 KouXin > Permissions, verify if the app has Contacts or Read Contacts permission, or use ADB: adb shell dumpsys package com.qihoo360.kouxin | grep -i contactAffected if The app holds contacts-related permissions (READ_CONTACTS, WRITE_CONTACTS)
-
Examine app data storage for sensitive data exposureUsing a file manager with root access or ADB, navigate to /data/data/com.qihoo360.kouxin/ and inspect the shared_prefs or databases folders for unencrypted SMS or contact filesAffected if SMS or contact data files exist in plaintext/unencrypted form within the app's private directory
If the 360 KouXin app version 1.5.3 is installed and holds SMS or contacts permissions, the device is affected by this vulnerability.
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 update to a patched version of the application. Developers must implement proper encryption for stored data (especially SMS and contacts), use Android's secure storage mechanisms (EncryptedSharedPreferences), and enforce appropriate access controls.
- 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-4772 — 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-4772 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