RealTek SDK Introduces Vulnerability In Some Routers
jones_supa writes: SOHO routers from manufacturers including at least Trendnet and D-Link allow attackers anywhere in the world to execute malicious code on the devices, according to a security advisory issued over the weekend. The remote command-injection vulnerability resides in the "miniigd SOAP service" as implemented by the RealTek SDK. Before someone asks, there is no comprehensive list of manufacturers or models that are affected. Nerds may be able to spot them by using the Metasploit framework to query their router. If the response contains "RealTek/v1.3" or similar, the device is likely vulnerable. For now, the vulnerable routers should be restricted to communicate only with trusted devices. HP's Zero Day Initiative reported the bug confidentially to RealTek in August 2013, but the issue was disclosed 20 months later as no fix has been provided.
should be restricted to communicate only with trusted devices
Sounds like a good policy anyway.
You can't trust "realtek", they are everywhere yet none of their products are worth a dime.
TFA says 2014, not 2013. And thus, not 20 months later.
My blog: http://www.seebs.net/log/ --- My iPhone/iPad app: http://www.seebs.net/seebsfrac/
Whoever trusts router security to some (especially american or chinese) company is a moron. Use open source firmware like openwrt or ddwrt and dont buy routers that don't support some kind of open source firmware. Vote with your wallets god damn it!
And I knew it was a good idea to go for AVM's Fritz!Box-es...
(regular updates even for old models, no market segmentation where models only differ by firmware, trying to cram as much feature in one model as possible instead of launching 20 subtly different models, etc.)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
So I wonder if my Trendnet router I just bought a couple months ago is vulnerable? I definitely have seen some strange stuff on router logs of late. But the router is most certainly a POS I would not advise anyone to buy a TEW-813DRU. I mean the darn thing can't even check for firmware updates and I make setting changes and select apply and the changes never set. Very flaky firmware for sure. I can see why its vulnerable.
You could do that, or you could buy a router pre-configured with OSS from the factory. It's not even expensive at ~ $50.
I bought a similar model about a year ago, and its large antennas and decent range/speed make it the best router I've yet had. If it's not even more expensive, why not support a vendor that supports (more) secure, Open Source solutions?
I have no relationship with this vendor other than being a happy customer
I have no problem with your religion until you decide it's reason to deprive others of the truth.
So, are any of these router vulnerabilities relevant if I just put my xDSL modem/router into the bridged mode, and use another, patched router behind it if necessary?
That's The First Time I've Seen That Happen To RealTek. Or Is It Just In The String??????? Help Jaden Smith Out
Maybe they're not using SDK to mean the same thing we might have in mind
Security-Disabling Kit
The RTL8xxx chipset is also used in adapter cards. Does this vulnerability need the SDK specifically, and wouldn't a flash of dd=wrt to take care of the problem?
It's even worse, because unlike a lot of other gear, they can actually fix the problem in the field. They don't have to do a physical recall like car companies do. What they need is remote update features.
I think it goes back to Windows. Gates and friends set the standard that computers would break, and that the users had no recourse. If it crashed and you lost something important you were just out of luck. No guarantee on anything.
Now that everyone has accepted that manufacturers have no responsibility, we are completely stuck with infrastructure that makes it impossible to have secure online transactions. Users are deliberately kept in the dark and known bugs remain unfixed.
Until there is some change in the law that places liability where it belongs, on the manufacturers, nothing will change. Given the current political climate there is no chance of change. We're just screwed.
Why is Snark Required?
This is our hardware. We made it, we're going to have a backdoor into it.
Sounds like software defined networking to me :)
I'm a Linux user and the Bluetooth portion of the card is a null device and I have to restart the wireless network several times every hour.
If I replace the card with something that works, like Intel, it will not boot. Thanks Lenovo! Hard coding RealTek network card to the BIOS made me hate everything Lenovo.