Secure String Functions in the C Run-Time Library
Any function that modifies a string exposes a potential danger: if the destination string buffer is not large enough to contain the resulting string, memory corruption occurs. Here is an example:
// The following puts 4 characters in a // 3-character buffer, resulting in memory corruption WCHAR szBuffer[3] = L""; wcscpy(szBuffer, L"abc"); // The terminating 0 is a character too!
The problem with the strcpy
and wcscpy
functions (and most other string manipulation functions) is that they do not accept an argument specifying the maximum size of the buffer, and therefore, the function doesn’t know that it is corrupting memory. Because the function doesn’t know that it is corrupting memory, it can’t report ...
Get Windows® via C/C++, Fifth Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.