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
Description: The result of this call to malloc() is not checked for success before being used. This can result in application instability or crashing if memory is not available.
Remediation: Be sure to check the result and make sure it is correct before use. Some functions return a pointer which should be validated as not NULL before use. Other functions return integers or Boolean values that must either be zero or non-zero for the results of the function to be used. Consult the API documentation to determine what a correct result is from the function call. Note: These flaws were previously reported as CWE 391. Following Mitre decision to plan for deprecation of CWE 391, CWE 252 was identified as re-categorization for these findings.
Unchecked Malloc can sometimes be a big problem. I don't think this is really important to check here, but I wanted to be sure you knew this was being flagged in the Veracode security scanner.
The text was updated successfully, but these errors were encountered:
https://github.com/getsentry/sentry-cocoa/blob/main/Sources/Sentry/SentrySessionReplaySyncC.c#L24
Veracode Flaw info:
Unchecked Malloc can sometimes be a big problem. I don't think this is really important to check here, but I wanted to be sure you knew this was being flagged in the Veracode security scanner.
The text was updated successfully, but these errors were encountered: