NVG510 Remote Exploit Page Is Broken

Update It's fixed now. Forget about this post. See http://lastyearswishes.com/blog/view/4ff4c02e4aa5d808c569c1c9

I'm not quite for sure as to how, but the NVG510 U-Verse modem telnet-enable exploit page is for whatever reason now broken. I don't believe the NVG510 got patched. I only tested the page with Firefox 12 and now that Firefox 13 is out, it doesn't appear to work. Note, the exploit is still open and such, just my HTML Complete_Control page no longer works properly

I'm completely baffled as to why my exploit page isn't working anymore, but I can offer you a short term work around if you are semi-familiar with HTML and are a bit brave.

Go install the Firebug extension for Firefox. After you restart firefox load up the etherlan.ha page. Right click on the first ethernet drop-down box. and click inspect element with firebug You should see this: <select class="long" name="phy.enet[1].port[1].media"> Click over the "phy.enet[1].port[1].media" and change it to "mgmt.shell.telnet-port" And then push the little + button to expand the HTML tree. At the bottom of the expanded tree you should see <option selected="selected" value="auto">auto</option>

Click over the value="auto" (click the first "auto") and change it to "23"

After you get that done, push the Save button and this should for surely work, but it's definitely more complicated.

Posted: 6/27/2012 9:06:26 PM

Comments

Vijay
This worked like charm. I used chrome browser. I used chromes built in capability to 'inspect element' (available via right click on any web page) to edit the values as suggested. Now I am able to telnet in to the device. Thank you very much for the articles.
6/29/2012 5:12:49 AM
Anonymous
Not sure if it will work for you, but on your complete_control page you are posting to ethconfig.ha or something like that.  I made it work by changing your form to post to etherlan.ha.  Maybe they had an update?
7/4/2012 6:12:39 PM
Anonymous
When I override the DNS settings and set override-allow to on, my settings are still overwritten by ATT's dhcp settings for some reason.  Any ideas?  Thanks for your awesome guides.  It's the best resource on the entire internet for this  piece of hardware.
7/4/2012 6:17:09 PM
Earlz
@Anonymous(1) heh good point there.
7/4/2012 10:05:03 PM

Posting comments is currently disabled(probably due to spam)