CVE-2020-11539: An issue was discovered on Tata Sonata Smart SF Rush 1.12 devices
CVE-2020-11539 is a high-severity flaw (CVSS 8.1) affecting sf rush smart band firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered on Tata Sonata Smart SF Rush 1.12 devices. It has been identified that the smart band has no pairing (mode 0 Bluetooth LE security level) The data being transmitted over the air is not encrypted. Adding to this, the data being sent to the smart band doesn't have any authentication or signature verification. Thus, any attacker can control a parameter of the device.
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
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-11539?
sf rush smart band firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-11539 being exploited?
CVE-2020-11539 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-11539 affect?
CVE-2020-11539 affects sf rush smart band firmware. Severity is high (CVSS 8.1). An issue was discovered on Tata Sonata Smart SF Rush 1.12 devices. It has been identified that the smart band has no pairing (mode 0 Bluetooth LE security level) The data being transmitted over the air is not encrypted. Adding to this, the
How urgent is CVE-2020-11539?
Priority 49/100. High severity; Public exploit reference