CVE-2020-12730: MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.
CVE-2020-12730 is a medium-severity flaw (CVSS 5.3) affecting flamingo 2 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.3 (Medium) |
| Attack vector | Adjacent network |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 90%) |
| CISA exploited list | No |
| Weakness | CWE-319 |
| Published | 2021-07-15 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-12730?
flamingo 2 firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-12730 being exploited?
CVE-2020-12730 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-12730 affect?
CVE-2020-12730 affects flamingo 2 firmware. Severity is medium (CVSS 5.3). MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.
How urgent is CVE-2020-12730?
Priority 21/100. No elevated risk signals yet.
Related CVEs
- 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-12729 MEDIUM 4.6 MITIGATE MagicMotion Flamingo 2 has a lack of access control for reading from device descriptors.