[fpp]

sounds familiar - we found that one 1996 when doing system programming on NT (NuMega SoftIce was your best friend together with material published by Mark Russinovich prior of him working with MS - remember when you were doing e.g. a file system driver at that time there was close to zero documentation by MS and half of what they provided was wrong). Demonstrated then how to use it to log onto remote Windows systems over the I-Net and gain Admin rights. I thought this one with all what was published about it long ago would be well known since.

Astounded that it took so long to fix and that it passed on through generations of Windows version.

Almost certain similar can be said of other low level "bugs".

[hexadecimated]

How do you know it's the same bug?

[fpp]

same result - only one issue like that known to me So of course I could be wrong and this issue is not the only one in that protocol implementation / sys component(s)

[MichaelMoser123]

SMB protocol was a well known source of bugs, lots of service packs used to patch this service (funny that it was enabled on network facing machines. I think it was because windows server needed to be ready for every use case. They could have had it easier by having a separate windows product with non essential services disabled by default)