Forum Home
Press F1
 
Thread ID: 58625 2005-06-06 21:35:00 Heads Up: DSL Router Vulnerability. Murray P (44) Press F1
Post ID Timestamp Content User
361768 2005-06-08 06:46:00 There's not need to get cross with each other. ;)

Default account name and passwords are always going to be with us. How else do you make a system secure by setting safe passwords and other settings if there isn't a way to get in. It often happens that passwords are forgotten. People die. People leave employment. There has to be a way to reset to a known configurartion. Because that's a known configuration (with or without passwords) it is not a secure one.

There will always be people who don't read the instructions. There will always be people who read, then ignore the instructions. A small minority will have secure systems. ;)
Graham L (2)
361769 2005-06-08 09:32:00 Wow - once again.

If it came across as arrogant, then I apologise - as I will again and again:

Perhaps, Murray P, you responded so because you felt that my post was an attack on you? I feel that you have alot of personal angst, for to take this post and defend with such vigour? I'm sorry I struck a nerve, I mean no harm. Whatever the reason, I apologise. I sought not to criticise - my issue was simply that this is not new, and that it has been a long time threat. Although it is as real as ever, I was dictated by the cynicism I felt at the time to - with what could be taken ( and was taken ) as blatant arrogance - reiterate the fact that the threat is far from brand new, and is something we've had to deal with for much time, and will for much more time. This is something Chill himself said, but in less a caustic tone (and I commend him for it). Infact I went on to say exactly what you yourself did - although it may not appear as such.


well it might of been so last year, but just goes to show whats out there. I completely agree, that's what I was trying to say. No contradiction necessary.


Do you stop helping because a vulnerability was common knowledge to some here last year? Because the same stupid virus or dialler has struck again, because someone has a BIOS glitch that was patched years ago but only became apparent when they installed new hardware. Maybe we shouldn't shouldn't help people who use Win98, it's so passe, were're too 1337 to bother our heads with it.You mentioned that my post was a handy example, and used it to deal with the group of posters you claim to fit the above description. That's fine - but let it be known that at no stage did I complain, at no stage did I refuse help, at no stage did I deny the value of this thread or its contents. Infact I love old-school.

Never, I assure you, would actually use the term "so last year" in self righteous manner, or in any manner not meant as a joke - for that would be actively encouraging the blatant Americanisation (no 'z') that our society frequently faces.

In the end I think I've become the target of alot of built up anger for what I thought was an innocent - if not a poorly targeted - joke. I apologise, but you need not lecture me further.
Growly (6)
361770 2005-06-08 10:40:00 so if you change the default password AND

disable HTTP Remote Access does this fix the vunerability???

OR do you have to change the port for remote access even though it is disabled?

M.
Mantis (3703)
361771 2005-06-08 11:30:00 so if you change the default password AND

disable HTTP Remote Access does this fix the vunerability???

OR do you have to change the port for remote access even though it is disabled?

M.

One of the points is, this router has shipped with a firmware version that does not allow you to disable remote access.

Growly, take the word "example" literally, I include Chill and anyone else who dismissed the issue in jest or otherwise. If you want to take it individually I feel I said enough to point out otherwise.

Yep, I get pissed off from time to time and the attitude displayed by some in this thread did that for me, for sure. But no, I did not take it as a personal attack, I do not have alot of personal angst, or collective for that matter and do not usually go around dissing people (not here anyway).

The only reason I got peeved was because a number of people "apparently" dismissed the issues and therefore downgraded an alert that will be relevant to a lot of people regardless of how "known" it is or, how trivial it is to rectify (except for the firmware fault that some still haven't caught on to).

Anyway, the benefit of the tiff, is that the thread has been kept alive for a little longer than it might have been so, good on ya everyone :thumbs:
Murray P (44)
361772 2009-01-15 01:03:00 hi,

I just discovered this vulnerability on my dsl-504g router after doing a port scan. I have changed the password, disabled http remote access and changed the port number. Now can't access the routers web interface at all. I thought 'remote' meant via the internet. Can I regain access to the routers settings? Do I even need to??

I realize I have been open to intrusion for a long time! Is there anything I need to check see if anyone still has access to my pc? the sheildsUP port scan now says port 80 is 'stealth'.

thanks for your time,
jas
jasinspace (8290)
361773 2009-01-15 01:15:00 hi,

I just discovered this vulnerability on my dsl-504g router after doing a port scan . I have changed the password, disabled http remote access and changed the port number . Now can't access the routers web interface at all . I thought 'remote' meant via the internet . Can I regain access to the routers settings? Do I even need to??

I realize I have been open to intrusion for a long time! Is there anything I need to check see if anyone still has access to my pc? the sheildsUP port scan now says port 80 is 'stealth' .

thanks for your time,
jas

What did you change the port number to?

You will need to enter it when trying to access the routers config page .
EG: If you changed the port number to 8080 and your routers IP address is 192 . 168 . 1 . 1 then enter this in your internet browser:

192 . 168 . 1 . 1:8080
CYaBro (73)
361774 2009-01-15 01:18:00 You can always do a Factory Reset to bring things back to normal :) Chilling_Silence (9)
361775 2009-01-15 04:19:00 thanks guys. all sorted now :) jasinspace (8290)
1 2 3