These are the most common vulnerability classes we encounter across IoT device audits:
Hardcoded credentials in firmware (/etc/passwd, config files)CRITICAL
Stack/heap buffer overflow in firmware binary parsers - direct RCE candidateCRITICAL
Unsigned or improperly verified firmware update mechanism - arbitrary code execution via malicious updateCRITICAL
Unauthenticated firmware update endpoint - no credentials required to flash arbitrary firmware over the networkCRITICAL
UART / JTAG debug interface active in production buildCRITICAL
Command injection via web management interface input parametersCRITICAL
Shared cryptographic keys across all units of a modelCRITICAL
Use-after-free in embedded HTTP server or protocol handlerHIGH
Integer overflow in network packet parsing routinesHIGH
Unencrypted device-to-cloud communication (HTTP, MQTT)HIGH
Format string vulnerability in logging or diagnostic functionsHIGH
Insecure Direct Object Reference (IDOR) in cloud companion APIHIGH
BLE replay attacks due to missing nonce/timestamp validationHIGH
Race condition in privilege-sensitive firmware operationsHIGH
Authentication bypass in web management interfaceHIGH
Outdated / end-of-life OS and library versions with known CVEsMEDIUM
Unnecessary services running in production (Telnet, FTP, SNMP)MEDIUM
Verbose error messages leaking firmware version and stack tracesMEDIUM
Insecure default configuration with no enforced hardening baselineMEDIUM