magicsmotion vulnerabilities
Recent CVEs affecting magicsmotion products. 3 tracked.
magicsmotion has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2021-07-15. Highest priority: CVE-2020-12731 (score 44/100).
- CVE-2020-12731 HIGH 7.5 MITIGATE The MagicMotion Flamingo 2 application for Android stores data on an sdcard under com.vt.magicmotion/files/Pic
- CVE-2020-12730 MEDIUM 5.3 MITIGATE MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.
- CVE-2020-12729 MEDIUM 4.6 MITIGATE MagicMotion Flamingo 2 has a lack of access control for reading from device descriptors.
FAQ
How do I fix magicsmotion vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is magicsmotion being exploited right now?
None of the tracked magicsmotion CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which magicsmotion CVE should I patch first?
CVE-2020-12731 currently ranks highest (44/100): The MagicMotion Flamingo 2 application for Android stores data on an sdcard under com.vt.magicmotion/files/Pic.