CEH Practice Question: Advanced Topics: Wireless, Cloud, IoT, Cryptography

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Firmware reversing

  Why this is correct

  Firmware reversing involves extracting the embedded software from an IoT device, often through JTAG, UART, or memory chip dumping. Attackers then use tools like Ghidra or IDA Pro to analyze the binary code, searching for hardcoded credentials, cryptographic keys, backdoors, or exploitable buffer overflows and format string vulnerabilities. This process can uncover critical weaknesses that allow unauthorized access or control over the device.

• ✗

  Container escape

  Why it's wrong here

  Container escape is a technique where an attacker breaks out of an isolated container environment (e.g., Docker, Kubernetes) to gain access to the underlying host operating system or other containers. While some advanced IoT edge devices might utilize containerization, the vast majority of traditional IoT devices, such as smart sensors, cameras, or home appliances, operate on embedded systems without containerized workloads, making this a highly atypical and generally inapplicable attack vector for the broader IoT landscape.

• ✗

  SQL injection

  Why it's wrong here

  SQL injection is a code injection technique used to attack data-driven applications, typically web applications, by inserting malicious SQL statements into an entry field for execution. While an IoT device might interact with a backend database or web service that *is* vulnerable to SQL injection, the attack itself targets the application layer of the server, not the embedded IoT device directly. Therefore, it's not considered a primary or direct attack vector *against* the IoT device itself.

• ✓

  Default credentials

  Why this is correct

  Many IoT devices are manufactured and deployed with easily guessable or universally known default usernames and passwords (e.g., "admin/admin," "root/password"). Attackers can leverage automated scanning tools and dictionaries to quickly identify and exploit devices still using these factory settings, gaining unauthorized administrative access. This widespread vulnerability stems from manufacturers prioritizing ease of deployment over robust security practices, and users often failing to change these defaults.

• ✓

  Insecure protocols (e.g., MQTT, CoAP)

  Why this is correct

  Many IoT communication protocols, such as Message Queuing Telemetry Transport (MQTT) and Constrained Application Protocol (CoAP), were designed for resource-constrained environments and often lack robust security features by default. MQTT brokers, if not properly configured with authentication and authorization, can allow unauthorized clients to publish or subscribe to sensitive topics, leading to data interception or command injection. Similarly, CoAP, often running over UDP, can be vulnerable to spoofing, replay attacks, or denial-of-service if not secured with DTLS.

Go deeper

Related to this question