Code Audit For Buffer Overflow

File Path: <PACKAGE_ROOT>\archive\document\devel\free_microsoft_visual_c_building_environment.html
Created inside Umbrella. Public Key Fingerprint for Identification: 3403 23D8 F4D2 1B25 D936 E4CF 7899 B782 F6F7 72D6, World Wide Web for Additional Information: http://umbrella.name/
Created by Liu Die Yu. Public Key Fingerprint for Identification: 02F8 E0DD A0C5 6DF5 0CDD EA63 C7DB E0EA D92A F9E0, Email Contact: liudieyu@umbrella.name
2005/02/19 - Modified by Liu Die Yu. Public Key Fingerprint for Identification: 02F8 E0DD A0C5 6DF5 0CDD EA63 C7DB E0EA D92A F9E0, Email Contact: liudieyu@umbrella.name
Please help us complete this page listing the usage of buffer writing functions in INSIDER.DLL. You can send report to info@umbrella.name. Original programmers can never perform sufficient code audit against code written by themselves, because they got prejudice(a partiality that prevents objective consideration of an issue or situation).
- Destination buffer contains enough space for data in source buffer?
- If only a part of data in source buffer is processed, this operation is a failure.
commonfun.cpp
- char * GetFullFileNameInCurrentFolder(char * sFileId,char *sOutputBuff, size_t nSize)
-
_strlwr(sFileId);
Executed after making sure sFileId is not null. So this fails if and only if caller supplied a wild pointer.
-
- char * GetCurrentUserName(void)
- char * GetMainModuleFileName(void)
- char * StripOutEndingNewLineChar(char * buff)
- char * GetFullFileNameInInsiderFolder(char * sFileId,char *sOutputBuff, size_t nSize)