News for hackers. Stuff that matters.

A comment on Integer overflow in glibc strncat. Parent comment

Re:Integer overflow in glibc strncat by jmgao on Tuesday December 22, 2015 @02:17PM (#10779661)
> Also note that SIZE_MAX is an unreasonable input, one would even say it violates preconditions.

Annex K adds rsize_t, RSIZE_MAX, and friends, which restrict inputs to reasonable values. Unfortunately, it doesn't retcon the old functions like strncpy, and worse, no one actually implements it.

[ Parent | on HN ]
Re:Integer overflow in glibc strncat by klodolph on Tuesday December 22, 2015 @03:30PM (#10780201)
No one? I thought Microsoft implemented it, or at least an early version thereof.
[ Parent | on HN ]
Re:Integer overflow in glibc strncat by cremno on Tuesday December 22, 2015 @04:32PM (#10780532)
A very early version. Among other differences the functions don't care about RSIZE_MAX (even though newer VS versions define and use rsize_t). However the Windows SDK contains <strsafe.h> which does limit the length of strings (STRSAFE_MAX_CCH).

https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...

[ Parent | on HN ]