News for hackers. Stuff that matters.
Re:The way Microsoft patched a recent bug raised some eyebrows by ggm on Tuesday November 21, 2017 @01:52AM (#15746173)
I'm having a senior moment here, but wasn't it common to include space in instruction-space and initialized data space, designed to permit binary patching by jump table to (currently) un-used pre-assigned regions?

I thought I'd even seen reference to support in compilers to pre-assign such spaces.

If (for instance) this is a product acquired from outside the Redmond campus, run successfully unpatched since B.C. and now needing work, it might actually be more effective to do what they did instead of reverse-compiling code, re-implementing, the whole shebang.

Security nightmare? Sure. Unsafe? depends. NASA pay old-timers the big bucks to keep things working out in space, which probably involves processes which aren't morally far removed from this.

Re:The way Microsoft patched a recent bug raised some eyebrows by kbenson on Tuesday November 21, 2017 @04:37AM (#15746798)
> I'm having a senior moment here, but wasn't it common to include space in instruction-space and initialized data space, designed to permit binary patching by jump table to (currently) un-used pre-assigned regions?

Are you referring to Microsoft's MOV EDI, EDI at the beginning of every function? That's a hot-patch point.[1]. I think that was more for in-memory patching to get around the problem that if you replace the current code, you might run afoul of some thread actually executing it. That wouldn't necessarily apply to the binary/DLL, which when loaded from scratch wouldn't need any such hot-patching.

1: https://blogs.msdn.microsoft.com/oldnewthing/20110921-00/?p=...

Re:The way Microsoft patched a recent bug raised some eyebrows by lower on Tuesday November 21, 2017 @04:33AM (#15746781)
> I'm having a senior moment here, but wasn't it common to include space in instruction-space and initialized data space, designed to permit binary patching by jump table to (currently) un-used pre-assigned regions

Maybe you're thinking about hot patch points in Windows DLLs?

https://blogs.msdn.microsoft.com/oldnewthing/20110921-00/?p=...