Thanks for the info! It's amazing he was able to reverse-engineer the setup installer to arrive at the conclusion.
I'm most interested in this topic because I'm working on the exact same task with AT&T Uverse router configurations. I posted my progress in http://www.backtrack-linux.org/forum...ad.php?t=50963 this thread.
I'm pretty sure the default WPA PSK is derived from the BSSID somehow, because the serial number is just the decimal form of the BSSID. Using some kind of hashing function makes sense, because it's easy to ensure uniform output. I don't think there is any setup executable available for these routers, but I'm excited to try some different hashing methods to see what I get.



Back in April 2008, Kevin Devine discovered that flaw (calculating the default password from the serial number) and created a PoC where you can calculate all possible default passwords based on the last 6 chars of the default SSID. Around 2009/2010, Thomson (I guess) fixed this issue by changing the last chars of the SSID to the last 6 chars of the AP's MAC address. This fixed the vulnerability found by Kevin, but I discovered that the router freely announces it's serial number through WPS. So I just had to check Kevin's discovery on how to calculate the default password from the serial number and ta-da! Vulnerability found. If you want, you can read more about Kevin's findings in the link posted by hannah. If you want a more hardcore explanation, you can read it here:
