Version: Smart Feature Phone 2.6
Gecko
| CVE ID | Reference | Severity | Patched Version / Tag | Note |
|---|---|---|---|---|
| CVE-2016-2827 | mfsa2016-85 | low | v2.6_dummy_tag | |
| CVE-2016-5270 | mfsa2016-85 | high | v2.6_dummy_tag | |
| CVE-2016-5271 | mfsa2016-85 | low | v2.6_dummy_tag | |
| CVE-2016-5272 | mfsa2016-85 | high | v2.6_dummy_tag | |
| CVE-2016-5273 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5276 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5274 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5277 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5275 | mfsa2016-85 | critical | v2.5 | |
| CVE-2016-5278 | mfsa2016-85 | critical | v2.5 | |
| CVE-2016-5279 | mfsa2016-85 | moderate | v2.6_dummy_tag | |
| CVE-2016-5280 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5281 | mfsa2016-85 | high | v2.5 | |
| CVE-2016-5282 | mfsa2016-85 | moderate | - | unrelated product |
| CVE-2016-5283 | mfsa2016-85 | high | - | pending |
| CVE-2016-5284 | mfsa2016-85 | high | - | excluded component |
| CVE-2016-5256 | mfsa2016-85 | critical | v2.5/v2.6_dummy_tag | |
| CVE-2016-5257 | mfsa2016-85 | critical | v2.5/v2.6_dummy_tag | |
| CVE-2016-5250 | mfsa2016-86 | moderate | v2.5 | |
| CVE-2016-5261 | mfsa2016-86 | high | v2.5 | |
| CVE-2016-5287 | mfsa2016-87 | high | - | unaffected, introduced by changesets of later version |
| CVE-2016-5288 | mfsa2016-87 | high | - | unaffected, introduced by changesets of later version |
| CVE-2016-5296 | mfsa2016-89 | critical | v2.5 | |
| CVE-2016-5292 | mfsa2016-89 | high | v2.6_dummy_tag | |
| CVE-2016-5293 | mfsa2016-89 | high | - | excluded component |
| CVE-2016-5294 | mfsa2016-89 | high | - | excluded component |
| CVE-2016-5297 | mfsa2016-89 | high | v2.6_dummy_tag | |
| CVE-2016-9064 | mfsa2016-89 | high | - | excluded component |
| CVE-2016-9065 | mfsa2016-89 | high | v2.6_dummy_tag | |
| CVE-2016-9066 | mfsa2016-89 | high | v2.5 | |
| CVE-2016-9067 | mfsa2016-89 | high | - | unaffected, introduced by changesets of later version |
| CVE-2016-9068 | mfsa2016-89 | high | v2.5 | |
| CVE-2016-9072 | mfsa2016-89 | high | v2.6_dummy_tag | |
| CVE-2016-9075 | mfsa2016-89 | high | - | excluded component |
| CVE-2016-9077 | mfsa2016-89 | high | - | unaffected, introduced by changesets of later version |
| CVE-2016-5291 | mfsa2016-89 | moderate | v2.5 | |
| CVE-2016-5295 | mfsa2016-89 | moderate | v2.5 | |
| CVE-2016-5298 | mfsa2016-89 | moderate | - | unrelated product |
| CVE-2016-5299 | mfsa2016-89 | moderate | - | unrelated product |
| CVE-2016-9061 | mfsa2016-89 | moderate | - | unrelated product |
| CVE-2016-9062 | mfsa2016-89 | moderate | - | unrelated product |
| CVE-2016-9070 | mfsa2016-89 | moderate | v2.6_dummy_tag | |
| CVE-2016-9073 | mfsa2016-89 | moderate | - | excluded component |
| CVE-2016-9074 | mfsa2016-89 | moderate | v2.6_dummy_tag | |
| CVE-2016-9076 | mfsa2016-89 | moderate | v2.6_dummy_tag | |
| CVE-2016-9063 | mfsa2016-89 | low | v2.6_dummy_tag | |
| CVE-2016-9071 | mfsa2016-89 | low | v2.6_dummy_tag | |
| CVE-2016-5289 | mfsa2016-89 | critical | v2.5/v2.6_dummy_tag | |
| CVE-2016-5290 | mfsa2016-89 | critical | v2.5/v2.6_dummy_tag | |
| CVE-2016-9078 | mfsa2016-91 | critical | v2.5 | |
| CVE-2016-9079 | mfsa2016-92 | critical | v2.5 | |
| CVE-2016-9894 | mfsa2016-94 | critical | v2.6_dummy_tag | |
| CVE-2016-9899 | mfsa2016-94 | critical | v2.5 | |
| CVE-2016-9895 | mfsa2016-94 | high | v2.5 | |
| CVE-2016-9896 | mfsa2016-94 | high | v2.6_dummy_tag | |
| CVE-2016-9897 | mfsa2016-94 | high | v2.5 | |
| CVE-2016-9898 | mfsa2016-94 | high | v2.5 | |
| CVE-2016-9900 | mfsa2016-94 | high | v2.5 | |
| CVE-2016-9904 | mfsa2016-94 | high | - | pending |
| CVE-2016-9901 | mfsa2016-94 | moderate | - | excluded component |
| CVE-2016-9902 | mfsa2016-94 | moderate | - | excluded component |
| CVE-2016-9903 | mfsa2016-94 | moderate | - | excluded component |
| CVE-2016-9080 | mfsa2016-94 | critical | v2.6_dummy_tag | |
| CVE-2016-9893 | mfsa2016-94 | critical | v2.5/v2.6_dummy_tag | |
| CVE-2016-9905 | mfsa2016-95 | high | v2.6_dummy_tag |