-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device Discovery via TDDP #9
Comments
Ah thanks so much for this! |
Also check out this fresh vulnerability report: http://www.coresecurity.com/advisories/tp-link-tddp-multiple-vulnerabilities |
Device discovery doesn't need TDDP implementation, just a broadcast UDP packet to 255.255.255.255:9999. The devices will reply with usual payloads. Request payload: |
This has been implemented (not with TDDP though, but I'd say extra work on this is not worth the effort), so closing for now. |
Please help me with this exploit how to use it. |
https://www.softscheck.com/en/reverse-engineering-tp-link-hs110/#TP-Link Device Debug Protocol
It says the TP-Link Device Debug Protocol has the ability to discover devices inside the same broadcast domain. A reference implementation of the general protocol is available at https://github.com/softScheck/tplink-smartplug/tree/master/tddp-client.
The text was updated successfully, but these errors were encountered: