Connected Io vulnerabilities
7 known vulnerabilities in Connected Io from Connectedio. 7 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
Connected Io: Improper Neutralization of Argument Delimiters in a Command
Connected IO v2.1.0 and prior has an argument injection vulnerability in its AT command message in its communication protocol, enabling attackers to execute arbitrary OS commands on devices.
- 9.8 Critical severity
Connected Io: Improper Neutralization of Special Elements used in an OS Command
Connected IO v2.1.0 and prior has an OS command injection vulnerability in the set firewall command in part of its communication protocol, enabling attackers to execute arbitrary OS commands on devices.
- 9.8 Critical severity
Connected Io: Improper Neutralization of Argument Delimiters in a Command
Connected IO v2.1.0 and prior has an argument injection vulnerability in its iptables command message in its communication protocol, enabling attackers to execute arbitrary OS commands on devices.
- 9.8 Critical severity
Connected Io: Out-of-bounds Write
Connected IO v2.1.0 and prior has a stack-based buffer overflow vulnerability in its communication protocol, enabling attackers to take control over devices.
- 9.8 Critical severity
Connected Io: Improper Neutralization of Special Elements used in an OS Command
Connected IO v2.1.0 and prior has a command as part of its communication protocol allowing the management platform to specify arbitrary OS commands for devices to execute. Attackers abusing this dangerous functionality may issue all devices OS commands to exec
- 9.8 Critical severity
connected_io: Cleartext Storage of Sensitive Information
Connected IO v2.1.0 and prior keeps passwords and credentials in clear-text format, allowing attackers to exfiltrate the credentials and use them to impersonate the devices.
- 9.8 Critical severity
Connected Io: Use of Hard-coded Credentials
Connected IO v2.1.0 and prior uses a hard-coded username/password pair embedded in their device's firmware used for device communication using MQTT. An attacker who gained access to these credentials is able to connect to the MQTT broker and send messages on b