lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <41ED05A9F32CD411984A002035875DEB0724AD77@exchsrvnj.everestre.com> From: Andrew.Berges at everestre.com (Andrew.Berges@...restre.com) Subject: Allchin bug p-o-c. Hi, I'm rather new to this list, and I think I may have missed some of the background on this - could someone bring me up to speed as to what is happening here? Thanks for the help, Andrew Berges - Associate Manager, Systems Everest Global Services 908.604.3020 andrew.berges@...restre.com -----Original Message----- From: Dave Korn [mailto:davek_throwaway@...mail.com] Sent: Tuesday, October 07, 2003 6:56 AM To: vuln-dev@...urityfocus.com; full-disclosure@...ts.netsys.com Subject: [Full-Disclosure] Allchin bug p-o-c. Here's p-o-c code for the allchin vulnerability. It allows you to write a (fairly) arbitrary DWORD to a (also fairly) arbitrary address in the memory space of mqsvc.exe on a remote w2k server. It should be straightforward enough to turn that into any kind of remote shell sploit using the standard well known techniques (e.g. overwrite an exception handler) but I haven't done so yet. Interestingly enough, this works on sp2 but sp4 seems to be immune; I haven't tested sp3. I say 'interesting', because I can't find any reference to this bug having been fixed in the lists of bugs fixed in those service packs, but it's definitely been whacked in some way by sp4.... cheers, DaveK
Powered by blists - more mailing lists