Add Belkin Wemo UPnP RCE (tested on Crock-Pot) #11409
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version fragmentation frequently means that consumers are buying vulnerable IoT devices even if vulnerabilities have been disclosed and patched.
This is precisely what happened to us when we bought a new Wemo-enabled Crock-Pot from Amazon.
Through fuzzing and community research, we discovered that the Crock-Pot we purchased is vulnerable to a command injection vulnerability in its UPnP implementation... that was discovered by @phikshun in 2014 and patched by Belkin in 2015.
Consumers buying new IoT devices should be aware that their new devices aren't necessarily running new software. Patch early and patch often!
Thank you to @phikshun for the original research and UFuzz, which a friend and I hope to maintain and use in continued work!
See #10731 for the Crock-Pot remote control.