D-Link Routers Vulnerable To DNS Hijacking
An anonymous reader writes At least one and likely more D-Link routers as well as those of other manufacturers using the same firmware are vulnerable to remote changing of DNS settings and, effectively, traffic hijacking, a Bulgarian security researcher has discovered. Todor Donev, a member of the Ethical Hacker research team, says that the vulnerability is found in the ZynOS firmware of the device, D-Link's DSL-2740R ADSL modem/wireless router. The firmware in question is implemented in many networking equipment manufactured by D-Link, TP-Link Technologies and ZTE.
I get on my knees and give thanks to OpenWRT.
I actually specify Google's public DNS server in my computer's network config. The router's DNS is only there as a backup.
Also: Using D-Link? *tsk*
I've been working on various aspects of the CPE equation for almost 2 years now as part of the various OpenResolverProject, OpenNTPProject, and other related aspects. Most CPE can't even do DNS correctly, let alone securely.
Take Netgear for example, they can't even process RFC1035 4.2.2 correctly to say a client should support DNS over TCP (it's not just for zone transfers), but instead of just not responding, or sending back some error that allows the DNS client to try the next resolver it has, you get it sending REFUSED: https://www.cloudshark.org/cap...
These devices are unmaintained outside of the few who actually upgrade them, and it's most likely still got default passwords on it causing all sorts of other possible pain and xss abuse/malware concerns. This is only going to get worse as more things have an IP address and communicate with the rest of the world.
So it seems hackers have found yet another way to attack us. Its weird because I was dealing with some strange stuff on a D Link log a while back. It was like a DOS attack only it wasn't, but it was coming from one address so I simply blocked that address and stopped it. I never used to pay much attention to router logs, but I guess its just another place to check.
Why leave remote administration on?
I would avoid opening the web UI of any home router on the WAN side.
It's mostly unnecessary and a needless security exposure.
.
guys, I'm using dsl-2741b how do I discover if it use zynos or not?
other than that, can you recommend good dsl router? I was looking at asus...
he be ETHICALLY haxxin!!!1!
Put OpenWrt on it and problem over.
Slashdot, fix the reply notifications... You won't get away with it...
What can you do with this usb vga dongle ? does openwrt have drivers ?
> The firmware in question is implemented in many networking equipment manufactured by D-Link, TP-Link Technologies and ZTE.
So which models?
Publishing an exploit with out notifying the company first == DICK move.
My mother has a stock DSL-2640 ... is it vulnerable too?
Thou leaving remote admin open in that piece of junk wouldn't ever even cross my mind! :o
Where's all the comments about Donev not informing D-Link before releasing exploit code.
"The exploit was created by Todor Donev, member of a Bulgarian security research outfit called Ethical Hacker[...]"
"Donev did not report the vulnerability to D-Link and as far as he knows it is currently a zero-day[...]"
I don't think that word means what you think it means. :-/
Hosts do these things for more speed, security & reliability:
1.) Protect vs. malicious sites/servers (beyond malicious ads: See 2-10 next)
2.) Protect vs. fastflux botnets + stop communication to C&C servers
3.) Protect vs. dynamic dns botnets + stop communication to C&C servers
4.) Protect vs. DGA botnets + stop communication to C&C servers
5.) Protect vs. downed DNS (adds reliability)
6.) Protect vs. DNS redirect poisoned dns
7.) Protect vs. DNS amplification attacks
8.) Protect vs. trackers
9.) Protect vs. spam
10.) Protect vs. phishing
11.) Protect vs. bandwidth caps
12.) Get you past a dnsbl
13.) Keep you off dns request logs
14.) Speed up websurfing by adblocks & hardcoded fav. sites
15.) Work on ANY webbound app (think stand-alone email programs) multiplatform.
16.) Give you easily texteditor controlled data for the above
17.) Do all that & block ads (better than addons) more efficiently in cpu cycles + memory usage
* Bolded items concern DNS & how hosts protect you vs them!
APK
P.S.=> Browser addons don't do the above for you:
Ghostery's Advertiser owned - "A fox guards the henhouse"-> http://en.wikipedia.org/wiki/G...
AdBlock's 4++gb & 100% CPU usage flooring inefficiency -> https://blog.mozilla.org/nneth... + ClarityRay defeats it + it 'souled-out' & is crippled by default paid off to not do its job http://techcrunch.com/2013/07/...
BOTH do far less than hosts do & less efficiently - hosts by way of comparison, do MORE w/ less.
Both add complexity/room for breakdown/exploit + from a slower mode of operations (usermode = more messagepassing overheads vs. hosts in kernelmode).
Hosts start w/ the IP stack before REDUNDANT inefficient addons BEGIN to operate (as 1st resolver queried).
For the BEST hosts file?
APK Hosts File Engine 9.0++ SR-1 32/64-bit -> http://start64.com/index.php?o...
The BEST antivirus (MalwareBytes) http://www.av-test.org/en/news... recommend & host it http://hosts-file.net/?s=Downl...
... apk
I wish when people released exploits or news of exploits for home routers they would state if it is exploitable via the external port. This is all most people should care about.
If something is only exploitable via the web interface, or via an internal interface, the issue is considerably less interesting. This information needs to be front and center for all vulnerabilities of home routers. Frankly, I don't even want to hear about a vuln that requires access to the web interface. It's uninteresting, because giving non-trusted users access to the web interface is a misconfiguration in my book.