full-disclosure - RE: SMB overflow attacks

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: RE: SMB overflow attacks

John Schutz to Jason Coombs:

> > Does anyone have any information about why System binds to a port above
> > 1024
> 
> I believe the windows task scheduler will bind to a port above 1024.

The OP asked why System binds a high port.

I don't know.

But I do know that the task scheduler will show up in a task-to-port 
mapper with a name other than "System" (under Win2K it should be 
"MTask" or "mtask.exe" depending on the options/mapping tool used).  
This is often (even usually) port 1025 because the task scheduler 
loads early in the startup process and is commonly the first thing to 
persistently bind a high port.

On NT (and derived OSes) it is common/usual to see "System" bound to 
a port numbered slightly higer than the one the Task Scheduler gets.

Regards,

Nick FitzGerald