| Version | Supported |
|---|---|
| 1.0.x | ✅ |
If you discover a security vulnerability in MWT-1, please consider the following before reporting:
-
The model generates random text. If the random text happens to contain sensitive information, this is a statistical coincidence and not a data breach.
-
The REST API has no authentication. This is by design. There is nothing to protect. The worst an attacker can do is generate random text slightly faster than intended.
-
The WiFi credentials are hardcoded in the firmware. Yes. We know. The device costs $3. If someone steals your WiFi password from it, you have lost $3 and a WiFi password. This is not a CVE.
-
The ESP8266 has known vulnerabilities. The ESP8266 was designed in 2014. It has the security posture of a 2014 IoT device, which is to say, none. MWT-1 does not attempt to improve on this because it is a random text generator, not a security appliance.
MWT-1's threat model is as follows:
- Confidentiality: MWT-1 has no secrets. It has 150 words. They're in the source code. They're in the README. They're on the landing page. There is nothing to exfiltrate.
- Integrity: An attacker could modify the vocabulary list to include different words. The output would still be random text. The impact is negligible.
- Availability: An attacker could denial-of-service the ESP8266 by sending many requests. The device would stop generating random text. We do not consider this a meaningful loss.
If, despite all of the above, you still believe you have found a legitimate security vulnerability, please email jamesneawedde@protonmail.com with the subject line "MWT-1 Security" and we will respond with the gravity that the situation warrants.
We do not have a bug bounty program. The entire project costs $3. We cannot in good conscience offer financial rewards for finding bugs in a random number generator.