CEH Practice Question: Advanced Topics: Wireless, Cloud, IoT, Cryptography
An IoT device uses the MQTT protocol without TLS. A security tester connects to the broker and subscribes to all topics using '#'. What is the tester MOST likely able to accomplish?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Eavesdrop on all MQTT communications
MQTT without encryption allows anyone to subscribe to topics. Subscribing to '#' captures all messages, leading to interception of sensitive data. This is a passive eavesdropping attack, not active manipulation like replay or injection.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Perform a denial of service on the broker
Why it's wrong here
Simply subscribing to a topic, even a wildcard, is a standard client operation and does not inherently lead to a denial of service on the MQTT broker. While a massive flood of connection requests or subscriptions from numerous clients could potentially overwhelm broker resources, the action described is merely a single subscription. A DoS attack typically requires a sustained, high-volume malicious traffic generation or exploitation of a specific vulnerability, which is not achieved by a basic subscription.
- ✓
Eavesdrop on all MQTT communications
Why this is correct
Without TLS encryption, all MQTT communications are transmitted in plaintext over the network. By subscribing to the '#' wildcard topic, an attacker can receive every message published to the broker, effectively eavesdropping on all traffic. This allows the interception of sensitive data, operational commands, and device states, as the unencrypted protocol provides no confidentiality protection against network sniffers or malicious subscribers.
- ✗
Inject malicious control commands
Why it's wrong here
Injecting malicious control commands requires the ability to *publish* messages to specific topics that the IoT devices are subscribed to, not merely subscribing to topics. While an attacker might gain insight into command structures by eavesdropping, publishing commands typically requires authentication and authorization to write to those topics. A simple subscription only grants read access to messages, preventing direct command injection.
- ✗
Replay previously captured messages
Why it's wrong here
Replaying previously captured messages involves intercepting legitimate messages and then re-transmitting them later to trick the system into performing an action. While subscribing to '#' allows an attacker to *capture* messages, the act of *replaying* them is a distinct subsequent step that requires publishing capabilities. The immediate action of subscribing only facilitates observation, not the active re-transmission of data.
Go deeper
Related to this question
About these practice questions
One of 870 original CEH practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CEH practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CEH exam.