You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone.
Our customer used security scanners to check app for security issues. Our app used RamblerTyphoonUtils.
Scanner complained with:
Signed integer strlen at line 64 of /Pods/RamblerTyphoonUtils/Code/Testing/AssemblyTesting/RamblerTyphoonAssemblyTestUtilities.m specifies size of memory to allocate.
66. char buffer[1 + strlen(attributes)];
And I can agree that stack allocation with unpredictable length can be dangerous, or at least looks like.
I suggest removing that method for getting property type and use
Hi everyone.
Our customer used security scanners to check app for security issues. Our app used
RamblerTyphoonUtils
.Scanner complained with:
And I can agree that stack allocation with unpredictable length can be dangerous, or at least looks like.
I suggest removing that method for getting property type and use
for that.
Aslo see
I think these methods can be handy, since RamblerTyphoonUtils depends on Typhoon
The text was updated successfully, but these errors were encountered: