Centrino seems to have a wireless backdoor
One can break into someone else's Centrino notebooks in WiFi range without much effort. I think hackers must love that. Imagine one hacker was on board the same plane as, say, some dude with a lot of secrets. Assuming that dude's Centrino notebook didn't explode into flames, the hacker would have plenty of time getting into the notebook and retrieve data at relatively highspeed.
The vulnerability in the Intel Centrino wireless device driver could allow attackers within range of Wi-Fi signal to execute arbitrary code on the Centrino notebook. It is apparently a buffer overflow problem with Intel's code. All the hacker needs to do is send Centrino an oversized peice of packet with malicious instructions attached at the end. The Intel device driver code will then happily run the malicious code.
AMD's Turion 64 is immune from such bad behaviour because it's armed with NX-bit technology that can prevent execution of data. That's why you don't see similar reports for AMD64/Turion 64.
Intel's Centrino is a legacy 32 bit technology that doesn't have AMD NX. Intel has copied AMD NX bit in its newer EM64T implementaion on Netburst Pentium 4. It's unclear or unproven whether Intel's Conroe has correctly copied AMD NX.
posted by Sharikou, Ph. D. @ 8/04/2006 09:53:00 AM
53 Comments:
If you did a bit of research, you would discover that this is not a Centrino problem, but a WiFi problem that encompasses many machines including Macs.
But alas with your bias intact and your credibility at new lows, here is what you opt to post.
No surprise.
No, this is specifically an Intel Centrino "feature":
"Description:
Security vulnerabilities have been identified in the Microsoft* Windows* drivers for the Intel® 2200BG and 2915ABG PRO/Wireless Network Connection Hardware (w22n50.sys, w22n51.sys, w29n50.sys, w29n51.sys), which could potentially be exploited by attackers within range of the Wi-Fi station to execute arbitrary code on the target system with kernel-level privileges. These flaws are due to a memory corruption while parsing certain frames."
No it is not. Read the link, here is a snippet:
ACROSS THE BOARD. Maynor stressed that there was nothing Mac-specific in the attack. The problem was not in the OS X operating system from Apple (AAPL) but in the third-party "device driver" software. Although only Intel (INTC) has announced vulnerabilities, it seems a safe bet at this point that there are similar problems with any type of Wi-Fi radio working with any operating system, including any flavor of Windows or Linux.
http://yahoo.businessweek.com/
technology/content/aug2006/tc20060803_264406.htm
It's called a driver issue. If there was some ridiculous scumbag who lived only to post meaningless drivel and lies about AMD I'm sure he could post important sounding blatherings about how AMD CPUs used to explode and how they are insecure because of one issue.
You are a joke, and everyone who knows this blog knows it. It's amazing to me that you keep posting these lies. You do know that if you ever get off welfare and apply for a job people search for you on google? Imagine how quickly they'll laugh you out of the hiring office when they see these ridiculous lies of yours.
Ha ha ..a 129MB patch ..what is this a joke ...
I am beginnig to wonder ..how many folks working for the US govt carry a Centrino ..plenty I guess
129MB isn't nothing when they're on broadband anyways, not downplaying the flaw:)
The very first line in the link you point to says...
"Security vulnerabilities exist in the Microsoft* Windows* drivers ..."
Duh!!!
sorry to say shari..
but even tomshardware and other companies has talked about this..
its a THIRD PARTY SOFTWARE, in aTHIRD PARTY HARDWARE. thus can affect windows, MAC and even linux systems.
2915ABG PRO/Wireless Network Connection Hardware (w22n50.sys, w22n51.sys, w29n50.sys, w29n51.sys)
Intel retards pay attention: w22n50.sys, w22n51.sys, w29n50.sys, w29n51.sys. Just look at the filenames, you know these device drivers are specific to Intel cards. Now, if you are saying Intel don't know how to write device drivers for their own WiFi cards but needed to outsource others to do it, then Intel people are crackpots who charge a lot of money for crap.
but even tomshardware and other companies has talked about this..
Toms? Do they have enough education and IQ to challenge my analysis?
"Although only Intel (INTC) has announced vulnerabilities, it seems a safe bet at this point that there are similar problems with any type of Wi-Fi radio working with any operating system, including any flavor of Windows or Linux."
Is it not likely that similar devices/drivers will have similar vulnerabilities?
why don't you do a post on what Intel should be doing from a technology development standpoint as part of their future plans.
The only way for Intel to survive is to become a foundry for AMD. Anything Intel does now is too late. k8L is too advanced. and what AMD has for 2008 is even more advanced. It's beyond the reach of Intel folks.
Is it not likely that similar devices/drivers will have similar vulnerabilities?
Intel crackpots wrote bad code doesn't mean others also wrote bad code.
I am surprised how..Intel ass kissers like Business Week is downplaying this information. Here goes the title:
"Warning: Your Wi-Fi Is Vulnerable to Attack
As Intel announces chinks in its wireless radio software, researchers show how hackers can take control of even encrypted Wi-Fi laptops"
Here is what I note::
1.) No mention of the word "Centrino" in the title
2.) Using ambiguous words like "Wireless Radio software" - what the sh*t is that ?
My title would read like this:
"Centrino has a big hole, run to your nearest desktop and download the patch before even booting your lappy" and ..All you US govt employees don’t even go near a Centrino Laptop...
Imagine what would happen if a hacker hacks into a Paypal employee working on this Centrino laptop doing database maintanence!! ..sweet!!
Sharikou, Ph. D said...
"Do they have enough education and IQ to challenge my analysis?"
Here is a quote from Charles Caleb Colton (1780 - 1832)
"To know a man, observe how he wins his object, rather than how he loses it; for when we fail our pride supports us; when we succeed, it betrays us."
There is no questioning your intelligent, but your head is swelling.
Can a hacker cause a Dell laptop to explode by uploading codes to increase throttling, hence stressing the battery?
Just a joke, Intel fanboys. :)
129MB isn't nothing when they're on broadband anyways, not downplaying the flaw:)
What are you on ???
Driver files are like 1KB to a few 10s KB...Dude I think for you KB and MB are the same. aint it ??
--Wrong, this is a cross-platform, cross-chip manufacturer problem.
http://blog.washingtonpost.com/securityfix/2006/08/hijacking_a_macbook_in_60_seco_1.html
"The video shows Ellch and Maynor targeting a specific security flaw in the Macbook's wireless "device driver," the software that allows the internal wireless card to communicate with the underlying OS X operating system. While those device driver flaws are particular to the Macbook -- and presently not publicly disclosed -- Maynor said the two have found at least two similar flaws in device drivers for wireless cards either designed for or embedded in machines running the Windows OS."
"Apple -- like many computer manufacturers -- outsources the development of its wireless device drivers to third parties. In Apple's case, the developer in question is Atheros, a company that devises drivers for a number of different wireless cards, each designed with drivers specific to the operating systems on which they will be used."
Intel crackpots wrote bad code doesn't mean others also wrote bad code.
So Apple and the others that will come forth are crackpots.
All I've seen from AMD and folks like you is hype. Give us some benchmarks, documents, facts:)
Wrong, this is a cross-platform, cross-chip manufacturer problem.
Intel retards. Apple's problem is Apple's problem. Intel's problem is Intel's problem. Retards stick to each other. Apple and Intel are both crap, but that can't be generalized to the whole industry. Intel's press release stated clearly the flaw is in Intel's device drivers. The question is who wrote those device drivers for Intel's wifi cards. In either case, intel is crap.
Apple's problem is Atheros's problem, which has ties with Netgear, which has ties with everyone in Wifi:P
"Although only Intel (INTC) has announced vulnerabilities, it seems a safe bet at this point that there are similar problems with any type of Wi-Fi radio working with any operating system, including any flavor of Windows or Linux."
I'd rather believe Maynor of SecureWorks than you, though who would take your words to heart:P
paranoid thoughts:
GWB heads to Crawford, Otellini tags along.
BIG BUCKS to GOP campaign.
Soon DHS,FBI,CIA demand all USGOV computers/systems to use 'Core' CPUS.
0sama splits his gut laughing.
NUE atack b4 November selections ensures Supremes will designate (G0P) winners.
If U've ever used a portable john, U know it's not the cream that rises to the top.
"Although only Intel (INTC) has announced vulnerabilities, it seems a safe bet at this point that there are similar problems with any type of Wi-Fi radio working with any operating system, including any flavor of Windows or Linux."
The dude who said this has an IQ of -20. Intel's problem was clearly identified as a flaw in the device driver. Was this craphead saying Linux (which is open source) uses the same crap code for any wifi chip? Just look at this project for Broadcom WiFi chips (
http://linux-bcom4301.sourceforge.net/), you can see the some code is written from scratch.
"Until a driver is completed, there is a workaround for Intel/AMD-based computers called NdisWrapper, which allows you to use Windows drivers within Linux. This does not work for non-x86 architectures (ie Macs)."
Page last updated: May 9, 2005
"While work has previously been published on the Sourceforge CVS repository, we have transferred our efforts to a private server to avoid potential legal issues."
The driver isn't even functional and the source isn't viewable like you said.
owned.
The driver isn't even functional and the source isn't viewable like you said.
Crap head. I was just trying to illustrate that different devices may be based on different codes written by different people. For instance, Broadcom has its people writing device driver, Intel has its idiots writint device driver, there are open source folks writing device drivers... The fact Intel idiots wrote device drivers that have buffer overflow problems doesn't mean other people will make the same mistake. The conclusion by that low IQ retard that any device any OS has the same problem is just moronic. It's like saying two monkeys typed the same letter wrong at the same page. I am wasting my time explain this to you retards.
Funny how Intel apologists are trying to defend Intel. If Intel is boasting itself as a Wi-Fi leader with the much touted Centrino...woooooo
Cen..trin..no..then have to release a 129MB re-write(not just a patch). That's sad.
If you want people to take you seriously, you should consider backing yourself up with facts and stop calling names:)
The problem is a Wifi problem, not a processor problem, AMD notebooks using Atheros solutions or similar are at the same risk as all.
Of course different people make different drivers, so different that Intel and Atheros, and more to come are affected:P
Rather than constantly bash Intel with things you don't understand, please enlighten us on K8L, 4x4, K10 :)
I agree that this is a buffer overflow in the Intel's drivers and is therefore Intel's fault. However, I think that your comment about the lack of support for the NX-bit is incorrect. Pentium M is also supposed to have it since Dothan (only in 32-bit mode, of course :) ). And the real reason it didn't prevent the exploit is that AFAIK Windows doesn't use NX-bit protection for device drivers, only for user apps.
What he was also saying is it was a CPU security problem. Such as a AMD, it has no security problems because it doesn't allow a EXE to exicute in the buffer like a virus.
Intel chips however have this problem because the code and security buffer stinks. Thats another reason why the US goverment canned conroe. All they use is AMD for a reason. Your never going to see the us goverment use a conroe because its not MILITARY GRADE A MATERIAL. AMD's are much better for the US goverment. Best example, US goverment REJECTS CONROE. lol No more can be said. Theres nothing more to say.
One can see why the chinese were keen on avoiding any recommendations from Intel on wireless protocols.!
Pentium M is also supposed to have it since Dothan (only in 32-bit mode, of course :) )
No. Even according to Intel's specs, only some Core Duo chips support NX bit. Then, there is the question whether Intel was able to correctly implement it.
Windows XP SP2
uses NX bit to protect against buffer overflow in device drivers, so AMD64/Turion 64 will not have such Wifi problem at all. Only Intelers enjoy being hacked for being Intelers.
Toms? Do they have enough education and IQ to challenge my analysis?
I like how you always blame this on Intel's 32 bit hardware when it's a simple driver error.
It's not even a processor issue. It's a wi-fi driver issue, yet you go on to say:
Intel's Centrino is a legacy 32 bit technology that doesn't have AMD NX. Intel has copied AMD NX bit in its newer EM64T implementaion on Netburst Pentium 4. It's unclear or unproven whether Intel's Conroe has correctly copied AMD NX.
I fail to see any sort of connection to processor technology here.
I think Tom's has nothing to worry about.
Hey, of course you'll never address this just like you won't address any other part of this message, but whatever. How many hands on tests do you do personally? How often do you personally put a machine through it's paces?
Or do you choose to only go from second hand information. You claim that AT and Toms are biased, yet you do not challenge otherwise personally. Will you say that you can't buy a Conroe which is why you won't run a test?
According to your statistics, you should be able to buy a Conroe in no time. Remember? There's no demand! You posted this yourself.
Can you not afford to do this then? Is that the issue? Has your doctorate failed you? Oh, your doctorate hasn't failed you, right? You've got money.
Or are you broke? Not many real doctors are broke, unless they've got a mental issue. No mental issue, you say? Okay.
Well, if you can afford to do this then do it. What's that you say? No time? You spend all day posting messages around the internet, take a few hours off. We'll forgive you.
So in effect, you have no justifiable reason to not run your own tests, since you think everyone is biased.
Oh wait. You're biased, aren't you? You'd love nothing more than to see Intel go down. Or am I wrong?
Okay, okay, you're not biased. You'd be a fair tester. You'd let everyone here pick the benchmarks then, right? Sure, we'll figure it out while you're getting your AMD and Intel machine up and ready.
Bottom line is you whine constantly about Tom's and AT, but I haven't seen you post any benchmarks yourself.
I've been here long enough to discern a profile of you:
-You're about 24 years old.
-You are unemployed, partly because people don't like you because you feel that you're superior to other people, partly because you have nothing to speak about other than cpu's, and partly because you have no sense of humor.
-You have no degrees in anything.
-You have an obsessive compulsive disorder. Your basement, which you live in, is immaculate.
-Everything you've learned about CPUs is from the internet and other people, not from doing anything yourself.
-You are single because you are too manipulative to be in any sort of relationship.
Well, don't just sit there, you've got dusting and posting all over the net to do.
-You are unemployed, partly because people don't like you because you feel that you're superior to other people, partly because you have nothing to speak about other than cpu's...
...or maybe your assumption of him being unemployed is based on the words of some anonymous poster saying that Sharikou was fired and not so much on your great knowledge of psychology.
and partly because you have no sense of humor.
LOL! Sharikou has no sense of humor?! I bet you haven't seen Sharikou's phone conversation "transcripts"? :)
Doctor Doctor, lets take a look at two recent staments
"Toms? Do they have enough education and IQ to challenge my analysis?"
"The only way for Intel to survive is to become a foundry for AMD. Anything Intel does now is too late. k8L is too advanced. and what AMD has for 2008 is even more advanced. It's beyond the reach of Intel folks."
But Sharikou the Phd pretender who education and IQ is so high that he can't burden with us his degree, speciality, school. He is just so smart that he can't share facts.
Instead he shares opinions that are so farfetched the common man can't understand but the blind AMD fanboy eats of his backdoor.
How appropriate he titles this "..backdoor!"
Sharikou is far smarter, for more capable! He has a PhD. Yet he has no job, spends his days and nights screening posts and adding more comments on his blog.
Sharikou if you are so smart INTEL or AMD would have hired you. The fact you are here pontificating on the sideline tells you that neither AMD nor INTEL values anything you say here.
Sobering heah fanboys... if Sharikou had a real PhD, was as good/right as he claims to be he would be employed and helping change the world. Instead he yaps from the sideline criticizing and pretending to know all. The bottom line is he knows nothing has nothing of value to add to the real world.
He makes wild stupid staments like INTEL should foundry AMD's chip. INTEL is going bankrupt. COre2 benchmarks are all lies. Clearly a man with lots of vision.
Is that all your IQ can do. Show us how smart you are. Tell us what features INTEL should add to Core2 to compete against K8L. Tell us what INTEL's roadmap should do to compete against AMD ( the details, remember you are so smart). Then tell us what/should AMD do... ( remember you are so smart and know it all! ).
Now to reality, all the sites Sharikou degenerates do real work, provide the details, make a analysis based on data. Since these sites to gather real data it must be lies bribed by AMD. FUnny weren't these the same sites that told us how FX62 and Opetron were the winners over Pentium what only 6 months ago? What changed in those 6 months? AMD bribes stopped and INTEL bribes started. Funny I thought INTEL would have been smart enough to bribe these sites from the beginning to lie about AMD performance....
Notice no adds here. NO company would pay to have any banner associated with this. Kind of like going to a garbage dump.. you don't find billboards or advertisements there either.
Sharikou like his PhD is total fabrication, keep it up.
Oh.. this is also good!
"The dude who said this has an IQ of -20" Wow what is Sharkiou's IQ. Can you provide independent confirmation its above Forrest Gumps? If not at least tell us where and what you got your PhD in!
I know you can't divulge anything to substantaite your credibility, but I can count on you and your fanboys for a good laugh all day long. AFter all it would be no fun if we found out you had a PhD from some noname school for a total stupid PhD topic.
What a joke
How appropriate he titles this "..backdoor!"
I bet a lot of countries will investigate to see whether the security hole was deliberately planted.
No. Even according to Intel's specs, only some Core Duo chips support NX bit. Then, there is the question whether Intel was able to correctly implement it.
Some Pentium Ms are also supposed to have it, according to Intel:
http://www.intel.com/products/processor_number/chart/pentium_m.htm
Windows XP SP2 uses NX bit to protect against buffer overflow in device drivers, so AMD64/Turion 64 will not have such Wifi problem at all. Only Intelers enjoy being hacked for being Intelers.
While I wouldn't be very surprised if Intel didn't implement the NX-bit correctly, I'm not sure if I can trust Microsoft, either :)
Were these buffer overflows on the stack or on the heap? Is the heap also protected for device drivers? Anyway even if NX did work, it's still not an excuse for writing buggy drivers, because it would only prevent the attacker from taking control of the system, but he will still be able to crash them remotely, which is also not good.
I bet a lot of countries will investigate to see whether the security hole was deliberately planted
LOL.. tell us all about the plot.
You aren't man enough to tell us about your PhD.
Were you the same boy who never took a shower in the gym because you were ashmed of your body...
These bufferoverflow progamming errors are deliberate and crafted to be backdoors into anyone computers, any one who thinks that these are overlooked bugs is stupid when they are discovered to the general public then the smoke screen goes up..
Intel is dead, they are collapsing under its own weight, it won't live making a shitty chip that are unwanted by government. C2D will not make a difference as it is a small percentage of what Intel will sell. Netwurst is already too old, too shitty and slow. The ending is all too familiar too Motorola. Intel is dead as a old man with a heart attack
The 3 Laws of PC security:
1. Never assume your system is safe
2. If it's from Microsoft, it has holes
3. The older the password, the less secure the system.
Now i needa add a new one!
4. If you have Centrino, you are not safe from anything that uses buffer-overflow technology =)
is it me or the Turion is a big as* failure?
"Intel crackpots wrote bad code doesn't mean others also wrote bad code"
By the way Sharikou, I know the crackpots you are talking about are from your country.. The more you insult them, the more you insult yourself, crackpot!
"I am surprised how..Intel ass kissers like Business Week is downplaying this information. Here goes the title:"
the Inquirer downplays every bad news concerning AMD.. Remember the article where they talked about some recall on 3000 opterons for overheating.. It put a nice spin on it, too..
I think the debate about sharikous IQ or education has long passed.. Everybody knows that he does not have a PhD or even a Masters degree.. Most people doubt he even finished his B.S..
I am a technology fan boy.. I have an AMD, Apple, and Intel systems. The only problem I found among all these systems, was the OS..
But I guess it is a fair game the people keep wondering about Sharikou's IQ/education since he is not answering their questions about his quals.. If you back up your opinions with some PhD claims, it is fair to tell people what was it in and how it helps you back up your opinions.. If you do not back it up, well, nobody will take you seriously.
If you drop the Phd title, they may have more respect for you.
Dude, In all honesty, I do not tell people about this blog so it does not give AMD a bad picture about its supporters.. So, Shak, you are hurting AMD more than Intel.
Moderation is good
Dave says:
WiFi driver hacks are only the latest intel design problem. A few months back, A french government IT security service discovered a major hardware flaw in all pentium based processors. It was a legacy problem starting with P3 and continues up to Conroe. It may or may not have been removed in Conroe chips. Please refer to http://www.blogger.com/comment.g?blogID=18375538&postID=115471074597785869 If you put the two together, it is possible to hack into any networked active pentium based computer, and sieze administrative control. The theory is that a net worm could reproduce and attack that weakness, and kill almost every intel PC in a matter of weeks. That would make some headlines! It makes me real glad to have the "no execute" feature of my AMD chips to prevent such a possibility. I also have a temperature monitor installed on my desktop 3200+. It runs 24/7/365 with a stock AMD cooler. I have never seen the cpu temp rise above 131 degrees F, under any load, state or condition, even when the room temperature rose to 102 F ambient this week or the disks warm to 172 F under heavy read/writes.
The 129MB 'patch' is not for a simple driver problem, but something significant enough for Intel to change the complete driver system in order to fix it.
This is a DRIVER issue, not a hardware issue.
I also doubt Dr. Sharikou's credentials as a real Ph.D. would not use such insults as "all their programmers are idiots". If you've ever participated in any real debate at the doctoral level, the last thing you do is insult your opponents intelligence. You may disagree with their theory or conclusions, but in the end you are both seeking truth (or funding :) ).
If we want to talk about vulnerabilities, lets talk about the recently discovered "bluepill" that allows an undetectable rootkit to be installed via AMD's Pacifica virtualization on MS Vista.
Note that they call out Pacifica directly, not virtualization.
Hmmm.....
PhD..
I love yanking this guy.. PhD in title but with every post ony proves he has none.
This is more fun than when I was teasing the retarded geeks in grade school. Here the geeks talk back and give me a good laugh.
You know when you work hard changing the world and kciking your fanboys in the crouch. Its funny to come back and see you guys crouched over whimpering but still yelling nonsense.
Tell me any of you beside being a stupid bystander who buys computers if you know shit about the business of CPU design and what goes on inside IBM, AMD, or INTEL...
You don't... I do.
And the conclusions you make show you all don't know shit about the compromises and complexity invloved.
You all are entertaining.
Keep up the silly work.. LOL
The theory is that a net worm could reproduce and attack that weakness, and kill almost every intel PC in a matter of weeks.
Yes. A simple worm can infest all Intel computers, remain dormant at a set time, then all wake up do the following
1) disable thermal throttling
2) run the most thermally intensive code
The result: all Intel computers will melt down.
This could be a feature.
The theory is that a net worm could reproduce and attack that weakness, and kill almost every intel PC in a matter of weeks.
Yes. A simple worm can infest all Intel computers, remain dormant at a set time, then all wake up do the following
1) disable thermal throttling
2) run the most thermally intensive code
The result: all Intel computers will melt down.
This could be a feature.
Of all the things you've said on this blog Sharikou. That has got to be the STUPIDEST thing I've ever heard.
How old are you?
Me thinks about 14.
You may not be a Ph.D, but you are funny....
LOL.. the PhD says
"The theory is that a net worm could reproduce and attack that weakness, and kill almost every intel PC in a matter of weeks.
Yes. A simple worm can infest all Intel computers, remain dormant at a set time, then all wake up do the following
1) disable thermal throttling
2) run the most thermally intensive code
The result: all Intel computers will melt down.
"
Yes its a virus that cause the INTEL CPUS to do evil and bad things... are you kidding me!
What did I tell you guys? I get some serious entertainment here.
The more I yank the PhD the silly the things he says.
He got no PhD, he got no family, he got no life, all he got is a blog.
He got nothing to show for his sorry life..
So sad. I feel for your parents.. must live in shame.
Whats worst the shit or the flies that swarm around it?
He got no PhD, he got no family, he got no life, all he got is a blog.
He got nothing to show for his sorry life..
So sad. I feel for your parents.. must live in shame.
Whats worst the shit or the flies that swarm around it?
Words like these can only come from a miserable person with poorest of educations. If there's anyone you should be sorry about, it's the person you most often see in your mirror. I like this blog and read it often, though I disagree with some of the statements made by the author. The opinion expressed in this blog adds to the diversity of thought on the internet and we should all do our part to protect it.
Words like these can only come from a miserable person with poorest of educations.
Did you see the video of the Intel shareholder meeting? you can see those poor teardful Intel investors who were so mad, it's hilarious. They called for Paul O to be fired. I think the Intelers here should do more useful work by getting some firing done. I heard some AMD folks saying they are grateful to Craig and Paul...
Post a Comment
<< Home