News for hackers. Stuff that matters.
Re:Vulnerability in Microsoft TLS library could allow remote... by dmix on Tuesday November 11, 2014 @04:13PM (#8592208)
Triggers the tptacek bat signal (or other kind infosec people)

How worried should people reasonably be?

Re:Vulnerability in Microsoft TLS library could allow remote... by jeffmcjunkin on Tuesday November 11, 2014 @04:52PM (#8592455)
I'm not tptacek, but right now I think the answer is: "We don't know."

There isn't an acknowledged proof-of-concept, so we're not sure that it's exploitable. It hasn't been made clear whether it's wormable, either.

My bet is it will affect XP if it's exploitable, but only for those who added IIS (not default, and not terribly common). It will likely remain unpatched forever, as Microsoft is unlikely to send a patch to an "unsupported" OS again, like they did with the Internet Explorer 0-day [0]

[0]: http://blogs.technet.com/b/msrc/archive/2014/05/01/out-of-ba...

Re:Vulnerability in Microsoft TLS library could allow remote... by userbinator on Tuesday November 11, 2014 @07:44PM (#8593303)
It will likely remain unpatched forever

By Microsoft, but I'd bet someone else is definitely going to fix it and distribute a patch. If the amount of effort put forth by the Windows 98SE community in making unofficial patches that let much newer applications work is any indication (look up KernelEx and "98SE unofficial service pack"), XP is going to enjoy an even larger community of unofficial support.

Re:Vulnerability in Microsoft TLS library could allow remote... by cesarb on Tuesday November 11, 2014 @08:31PM (#8593488)
> exploitable, but only for those who added IIS

If I recall correctly, SQL Slammer also targeted a server component, but the vulnerable component was also present on some desktop systems, which were then affected.

It wouldn't surprise me if for instance some printer driver listening on a high port also uses the schannel component, and is thus vulnerable.

Re:Vulnerability in Microsoft TLS library could allow remote... by tptacek on Tuesday November 11, 2014 @05:45PM (#8592763)
I'unno. Looks pretty bad?
Re:Vulnerability in Microsoft TLS library could allow remote... by willvarfar on Tuesday November 11, 2014 @06:23PM (#8592987)
Can you go comment in the STARTTLS thread too please? ;)
Re:Vulnerability in Microsoft TLS library could allow remote... by AlyssaRowan on Wednesday November 12, 2014 @08:34AM (#8595332)
It is Very Bad Indeed™. It is exploitable to get RCE, so actually worse in impact than both Heartbleed and goto fail. (Other lesser, but still very serious effects like MITM are also implicated.)

IBM reported, MS did code review it seems, MS knew about some of these issues for ~6 months.

Patch immediately, people (like me) are running bindiff/etc and a public exploit won't be too far behind.

Not sure how far back it goes yet. All the way? The changes cover code going all the way back to the first SChannel code push, I think. (If XP is exploitable, this may be the XP killing vuln we've all been waiting for.)

Re:Vulnerability in Microsoft TLS library could allow remote... by swartkrans on Tuesday November 11, 2014 @04:17PM (#8592229)
Well it's patched now, but it didn't affect you unless you were running a "Windows Server" although all recent operating systems were affected. If your Windows machine is behind your home router and you were not forwarding ports to it you're probably fine. I doubt this vulnerability was known well enough that enough people were scanning for vulnerable IPs to exploit them.
Re:Vulnerability in Microsoft TLS library could allow remote... by xnull on Tuesday November 11, 2014 @04:54PM (#8592467)
The window from disclosure of patches to duplication is narrowing and it appears from the bulletin that client connections are affected as well. Furthermore any computer you take anywhere outside your home router (and can you really trust your home router as security boundary nowdays?!) will be easy to manipulate into an SChannel connection. Inside your home network, clients are still vulnerable to attack - any javascript/flash ad/referer can point a computer behind a router at an attacker server and serve up malicious SChannel packets. That is to say your home computer can be attacked on outgoing connections which your router will be happy to allow.

It's very serious. Patch immediately.

Re:Vulnerability in Microsoft TLS library could allow remote... by ars on Tuesday November 11, 2014 @06:07PM (#8592901)
Does this also affect firefox on XP? Does firefox use the Windows TLS library, or does it have its own?
Re:Vulnerability in Microsoft TLS library could allow remote... by xnull on Tuesday November 11, 2014 @06:23PM (#8592989)
It has its own ("Network Security Services" or NSS).

But that's not a reason to use Firefox on XP. ;)

Re:Vulnerability in Microsoft TLS library could allow remote... by benjaminRRR on Tuesday November 11, 2014 @11:04PM (#8593957)
For anyone that runs any web-facing IIS machines this has to be treated as a DEFCON 1 situation.