CVE-2011-0680 json
data/WorkingMessage.java in the Mms application in Android before 2.2.2 and 2.3.x before 2.3.2 does not properly manage the draft cache, wh…
published 2011-01-31 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0698
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
data/WorkingMessage.java in the Mms application in Android before 2.2.2 and 2.3.x before 2.3.2 does not properly manage the draft cache, which allows remote attackers to read SMS messages intended for other recipients in opportunistic circumstances via a standard text messaging service.
Patch / fix
Exploit prediction
1.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
theinquirer.net
/inquirer/news/1939386/google-updates-nexus-android-222
patch
- engadget.com /2011/01/22/nexus-one-gets-tiny-update-to-android-2-2-2-probably-fixes-sms/
- android.git.kernel.org /?p=platform/packages/apps/Mms.git%3Ba=commit%3Bh=4d26623ce82230e8e7009adb921c5edea370a9e0
- htcphones.net /nexus-one-update-to-android-2-2-2/
- twitter.com /GalaxySsupport/statuses/28078194607263744
-
securityfocus.com
/bid/46105
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/65125
vdb-entry
- phandroid.com /2011/01/21/android-2-3-2-update-pushing-to-nexus-s-phone-fixes-sms-bug/
- android.git.kernel.org /?p=platform/packages/apps/Mms.git%3Ba=commit%3Bh=18d6b7e9d2e538fb3c0264332b96c02abf367267
- samsunghub.com /2011/01/22/nexus-s-gets-android-2-3-2-fixes-sms-bug/
- code.google.com /p/android/issues/detail?id=9392#c1460
- code.google.com /p/android/issues/detail?id=9392#c1620
Sources
- CVE List CVE-2011-0680
- NVD CVE-2011-0680
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.