Crash: CRYPTO_malloc
Describe the bug The app crash when it detects a security threat.
To Reproduce The issue has been detected on some users through firebase crashlytics. I was not able to replicate the crash but from the logs I see that the problem always occurs on: screenRecording and screenshot.
Expected behavior I expect zero crashes
Screenshots
Please complete the following information: Crash: CRYPTO_malloc.txt
Additional context Also, trying to launch the debug app with Enable Address Sanitizer active I immediately get this crash
Hello @DevOpsAppsIOL , can you elaborate on how many devices does this crash occur (out of how many). Also the models and os versions of these devices? Thank you!
Kind regards, Talsec team
Hello @msikyna , The crashes occur on all iPhone/iPad models from the last 5 years and use these iOS versions:
- iOS 18.5.0
- iOS 18.4.1
- iOS 18.3.2
There are now about 208 devices with crashes and 210 events.
I see from the logs that before crashing there is the SecurityService Found incident: screenRecording log in 80% of cases. The remaining 20% have no log.
public func threatDetected(_ securityThreat: SecurityThreat) { CrashlyticsRecords.shared.log(msg: "SecurityService Found incident: \(securityThreat.rawValue)") .... .... .... }
Hi @msikyna, crashes are on the rise. I reached 700 crashes.
Hi @DevOpsAppsIOL
May I know what the version are you used in? Since I'm just starting implement for prevent screenshot and screen recording in my app and I don't want my app crash because this issue.
Thank you
Hi @arisupriatna14, I integrated the latest version (6.11.0).
Hello @DevOpsAppsIOL , thank you for adding details. Can you also supply how many running instances do you have? So we can estimate on what percentage of devices the incident happens. Moreover, did it also happen with 6.10.0 version? Thank you!
Hello @msikyna, we integrated your SDK for the first time starting from 6.11.0. We have reached more than 1000 crashes. The crashes concern about 1% of the total instances. The app is from https://www.italiaonline.it/ and has a very large audience.
Hello, we just released a new version. Could you try integrating it and see whether it solves the issue? Thank you! https://github.com/talsec/Free-RASP-iOS/releases/tag/v6.12.1
Hello @msikyna , Thanks for the new release. I hope it fixes the various crashes. I'll update you in the coming weeks.
Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.
Hello @msikyna , I need the whole month of September to understand if the problem has been resolved with the latest version. Thank you.
Hello @msikyna , Even with version 6.12.1 I'm having some crashes. I attached the stack file:
Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.
This is still happening.
Hello @msikyna, This is still happening.
I hope for a quick response from you.
Thank you
Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.
Update: We will be releasing a new SDK around this week that has a few fixes targeted to mitigate this issues. You can look forward to a new update this week.
Hello, a new release, 6.13.0 has been published, please try if the issue persists. Thank you!
Hello! This issue has been marked as inactive. If there is no further activity within the next 14 days, this issue will be automatically closed. If you believe this issue is still relevant and requires attention, please comment or provide additional information.
Hello! This issue has been closed. If you believe this issue is still relevant and requires attention, please reopen the issue.