The way they discovered it was that - and I'm not sure who it was.
Leo: Oh, there were worms floating around. Leo: And that's because there were websites already taking advantage of this right? There were sites out there that. Microsoft had to do the responsible thing, and call this critical, and push an out-of-cycle patch. So many things have happened to mitigate this being a problem, which is why, you know, I didn't immediately find, track you down and say, Leo, we've got to immediately alert our users to it. You know, file and printer sharing and other things.
#UTTARAN SERIAL EPISODE 168 WINDOWS#
That's the traditional Windows filesharing ports. So this is a - basically it's the service which is always lit, is always running and open and listening for things coming in on ports 139 and 445. The service that is exploitable, the remote procedure call, RPC service, it's sort of sandboxed so that it's not able to do as much damage as it can under 2000 and XP. Steve: It's the nature of the way they're running the service. Leo: So why? Is that because UAC pops up and says something's trying to access your system, or. It's reduced from critical to important on those platforms. The architecture of Vista, the updated security architecture mitigates the problem. It affects Windows 2000, XP, and Server 2003. It runs - it's an exploit in the RPC service that runs in all versions of Windows. Steve: Yeah, it is like one of the old-style, packet arrives at your computer. Because this is not a user goes to a bad website with their browser sort of problem. It is substantially different than, or more of a problem in some ways than referring to it during the Tech Guy stuff over the weekend when you were talking about it. Some people were saying, do you think Microsoft deliberately does this after Steve and Leo record the podcast, you know, like the moment after it's been recorded and before it actually goes public? Because this dropped out at exactly that time. And I picked up a little blurb in GRC's newsgroups.
#UTTARAN SERIAL EPISODE 168 UPDATE#
Leo: So let's get an update on what's been going on in the world of security, Steve Gibson. But we'll talk about all that, and also about some, well, there's lots of news in the last week since. Firefox users are essentially completely protected by recent updates to NoScript. The good news is there are things now that people can do. I mean, what we're going to talk about today, clickjacking, is very much like that. I mean, because what we're beginning to see now is that the technologies we rely on fundamentally are really being exploited. Leo: Well, lately it's been kind of bleak because it's like, there's bad stuff, and there doesn't really seem like there's any cure. Steve Gibson: Yes, in fact sometimes we're discussing things that you'd rather wish weren't the case.
And we do it with a guy who is the king, really, as far as I'm concerned, the man who discovered spyware, named spyware, wrote some of the most used security utilities out there, including ShieldsUP!, Mr. It's time for Security Now!, the show where we cover everything you'd ever want to know about security. This is Security Now! with Steve Gibson, Episode 168 for October 30, 2008: Clickjacking. Leo Laporte: Bandwidth for Security Now! is provided by AOL Radio at AOL.com/podcasting.
INTRO: Netcasts you love, from people you trust. Quarter size (16 kbps) mp3 audio file URL: High quality (64 kbps) mp3 audio file URL: Description: Steve and Leo discuss yet another challenge to surfing safely in the web world: Known as "ClickJacking," or more formally as "UI Redressing," this class of newly popular threats tricks web users into performing web-based actions they don't intend by leading them to believe they are doing something else entirely.
0 kommentar(er)
