Full Disclosure mailing list archives
Re: Another Low Blow From Microsoft: MBSA Failure!
From: Valdis.Kletnieks () vt edu
Date: Wed, 11 Feb 2004 09:12:09 -0500
On Tue, 10 Feb 2004 20:14:08 PST, morning_wood <se_cur_ity () hotmail com> said:
did you try exploit code to verify? that should dispel any ambiguity across scanner reports, it would be real easy to load your network hosts into a batch file or shell script and see how many "roots" you get.
Given the number of cases we see of somebody posting an actual PoC for a vulnerability that *doesn't* *work* on some machines, I'd really hate to bet my security on "Oh, the exploit we tried didn't work, we must be safe". Remember - if the exploit works, you have a problem. Failure of the exploit to work does NOT mean you don't have a problem - somebody with a different version that has a critical offset set to 4 more or less may make swiss cheese of your network.
Attachment:
_bin
Description:
Current thread:
- RE: Another Low Blow From Microsoft: MBSA Failure! Drew Copley (Feb 10)
- <Possible follow-ups>
- RE: Another Low Blow From Microsoft: MBSA Failure! Eric McCarty (Feb 10)
- RE: Another Low Blow From Microsoft: MBSA Failure! Drew Copley (Feb 10)
- Re: Another Low Blow From Microsoft: MBSA Failure! kevin hinze (Feb 11)
- Another Low Blow From Microsoft: MBSA Failure! dotsecure (Feb 10)
- Re: Another Low Blow From Microsoft: MBSA Failure! Byron Copeland (Feb 10)
- Re: Another Low Blow From Microsoft: MBSA Failure! morning_wood (Feb 10)
- Re: Another Low Blow From Microsoft: MBSA Failure! Valdis . Kletnieks (Feb 11)
- Re: Another Low Blow From Microsoft: MBSA Failure! Kenneth R. van Wyk (Feb 11)
- Re: Another Low Blow From Microsoft: MBSA Failure! morning_wood (Feb 11)
- RE: Another Low Blow From Microsoft: MBSA Failure! Evans, Arian (Feb 12)