OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
RE: [Dailydave] Microsoft letdown day

From: Aleksander P. Czarnowski (alekcavet.com.pl)
Date: Wed Jan 12 2005 - 10:35:16 CST


We're living in a strange world. Since DJB students advisory I am scared
of running nasm - good thing I am using masm32 on Windows system - DJB
and his students can't get me remotely any time soon ;-) However one
remote thing happened - a lot more people now know about DJB's security
mailing list. He's advertising genius.

Now I wonder how this bug will influence OpenBSD "Only one remote hole
in the default install, in more than 8 years!" slogan:

010: RELIABILITY FIX: January 10, 2005
A bug in the tcp(4) stack allows an invalid argument to be used in in
calculating the TCP retransmit timeout. By sending packets with specific
values in the TCP timestamp option, an attacker can cause a system
panic.

After all you can have a remote vulnerability even after you disable
(almost) every service (knowing how buggy those services plus kernel
are).
Just my 2 cents,
Cheers,
Alex Czarnwoski
AVET INS

> -----Original Message-----
> From: Dave Aitel [mailto:daveimmunitysec.com]
> Sent: 12 stycznia 2005 17:01
> To: dailydave
> Subject: [Dailydave] Microsoft letdown day
>
>
> I'm both happy and sad when there are no good Microsoft bugs. On one
> hand it's good that none of your bugs got blown (phew!), and on the
> other hand you don't have anything fun to do that
> day."Remote" bugs in
> IE just don't have that spark since five of them come out a week.
>
> One thing I've noticed is that it's now endemic that everyone agrees
> with DJB that client-side bugs like the ANI overflow are
> "remote bugs".
> This is crazy! I wonder if it's skewing any new "research" on
> "windows
> of vulnerability" or "The security of Linux versus Microsoft
> Windows".
> There are three simple classifications:
> Local
> Remote
> Client-Side
>
> An IE bug is not a remote bug. It's a client-side bug. I like
> how they
> claim there's "remote code execution." Is it making a DCOM call to a
> remote machine? :>
>
> If the industry can't even get this sort of thing right, how do we
> expect it to do something hard, like protect my Sidekick from
> getting owned?
>
> -dave
> _______________________________________________
> Dailydave mailing list
> Dailydavelists.immunitysec.com
> https://lists.immunitysec.com/mailman/listinfo> /dailydave
>
>
_______________________________________________
Dailydave mailing list
Dailydavelists.immunitysec.com
https://lists.immunitysec.com/mailman/listinfo/dailydave