- CopyAcceleratorTable can cause a buffer overflow because it uses an
commit9243c96e015a51b399194f62dd73d321d22e05b0
authorMike McCormack <mike@codeweavers.com>
Mon, 12 Jul 2004 20:42:30 +0000 (12 20:42 +0000)
committerAlexandre Julliard <julliard@winehq.org>
Mon, 12 Jul 2004 20:42:30 +0000 (12 20:42 +0000)
treec0d85672e1dd355a17b41030a1ec86f1df95825b
parent74cebde2918018be5e3f78ff61769a5e28a87214
- CopyAcceleratorTable can cause a buffer overflow because it uses an
  incorrect comparison between the number of accelerator entries
  available and the number of accelerator entries in the output buffer.
- My tests show that CopyAcceleratorTable always strips the high bit
  of the fVirt member of the accel struct.
- Calling DestroyAcceleratorTable with a NULL accelerator should
  return FALSE.
dlls/user/resource.c