Live data from Hacker News

How I Hacked a Router

disconnected.io

41–50 of 96 posts

Re: How I Hacked a Router

#41

One more reason to use NoScript - it would have made the CSRF significantly harder to pull off. And a reason to use an OS with a proper package manager, of course ;)

Not really. Depending on the protocol CSRFs are often an easy 1-click exploit on noscript-enabled browsers. Something like this:

    
       " />
      
    
Is the corresponding 1-click that works on noscript.

Re: How I Hacked a Router

#42
post #37

Earlier quoted context omitted.

Anybody that can run sendmail as root (or use an alternate program, or compile their own) can spoof the envelope sender.

Ah, gotcha. You're saying that you sent an email with a valid envelope sender from your domain, with only a spoofed From: address, and gmail sent it back. If so, nice!

Yep, exactly.

Re: How I Hacked a Router

#44
post #43

How much harder would this attack have been with a fully patched OSX Mavericks target and an Apple Time Capsule router?

Well, if his password was weak, easier than TFA.

I don't know about the vulnerabilities in the Time Capsule router, but from my understanding the only router firmware even remotely worth a look in terms of security would be OpenWRT.

Re: How I Hacked a Router

#45
post #38

Which one do you think will happen first: This guy goes to jail, or this guy gets a job offer?

Why would he go to jail? The guy's friend asked for the pentest. There was no "unauthorized access" involved here.

Re: How I Hacked a Router

#46
post #19

Sweet story ... and another vote for MikroTik routers for personal use.

I've seen MikroTik router mentioned on HN quite few times, and have been wondering how is it better compared to say, Broadcom-based routers running OpenWRT/Tomato/DD-WRT. Could you clarify why? (I've looked at RB750GL, which looks very interesting considering its price, but still don't know how would compared to my current ASUS RT-N16+Tomato setup.)

Re: How I Hacked a Router

#47
post #41

One more reason to use NoScript - it would have made the CSRF significantly harder to pull off. And a reason to use an OS with a proper package manager, of course ;)

Not really. Depending on the protocol CSRFs are often an easy 1-click exploit on noscript-enabled browsers. Something like this: " /> Is the corresponding 1-click that works on noscript.

Yep. XSS on the other hand would be very hard to pull off with NoScript enabled.

Re: How I Hacked a Router

#48
post #43

How much harder would this attack have been with a fully patched OSX Mavericks target and an Apple Time Capsule router?

Well, if his password was weak, easier than TFA. I don't know about the vulnerabilities in the Time Capsule router, but from my understanding the only router firmware even remotely worth a look in terms of security would be OpenWRT.

My cursory search suggests that it may be pretty secure: http://www.cvedetails.com/vulnerability-list/vendor_id-49/pr...

but I figured I should ask this guy, sounds like he knows what he's doing.

Re: How I Hacked a Router

#50

Everything is feasible except the faked linkedin email - it wouldn't pass SPF and so I'm pretty sure gmail would junk it.

In the comments section of the original article, the attacker (Phikshun) notes that he worked at the same company as his victim, so he was able to test the phish on himself to make sure it passed through that company's email security.
Post reply on HN