An issue was discovered on Tata Sonata Smart SF Rush 1.12 devices.

published 2020-04-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-3890

cvss: 8.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits: 0; none known

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.

Exploit prediction

1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/the-girl-who-lived/CVE-2020-11539/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.1	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	4.8	AV:A/AC:L/Au:N/C:P/I:P/A:N

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality
CWE-319 Cleartext Transmission of Sensitive Information
CWE-347 Improper Verification of Cryptographic Signature

References

github.com /the-girl-who-lived/CVE-2020-11539/
exploit, third-party-advisory
medium.com /%40sayliambure/hacking-a-5-smartband-824763ab6e8f

Sources

CVE List CVE-2020-11539
NVD CVE-2020-11539

Fencer Vulns 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.

Summary