Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Integrity threat not detected in iOS device || Expo React Native #68

Open
Mr-harsh10 opened this issue Jun 4, 2024 · 3 comments
Open
Labels
waiting for response Response from reporter is needed

Comments

@Mr-harsh10
Copy link

I am working on a React Native Expo app. During penetration testing, the tester was able to tamper with my app, rebundle it, and run it without any issues. I need to prevent this.

Dependencies
"expo": "^49.0.0",
"react-native": "0.72.10",
"freerasp-react-native": "^3.7.2",

@tompsota
Copy link
Member

tompsota commented Jun 4, 2024

Hello @Mr-harsh10,

Did you get any report from the penetration tester? It would be awesome if you could share with us how the tester was able to bypass freeRASP - i.e. which tools were used, which part of freeRASP was bypassed, etc.

You can also reach out to us at support@talsec.app - just please reference this issue.

Regards,
Tomas from Talsec

@Mr-harsh10
Copy link
Author

Mr-harsh10 commented Jun 5, 2024

Hello @tompsota thanks for the reply,
I don't know which tool was used by the testing team. But appIntegrity threat is detected successfully on android but not on ios.

which part of freeRASP was bypassed, - appIntegrity

@tompsota
Copy link
Member

tompsota commented Jun 7, 2024

Hello @Mr-harsh10,

We are aware that there are certain ways how to bypass freeRASP - and we are sure that experienced pentester will be able to bypass freeRASP.

If you are looking for a more advanced solution, take a look at BusinessRASP, which includes advanced protection of your app - including better resilience against bypassing - read more about the differences to freeRASP here and more about commercial offer here.

As long as you don't provide us any data about how (at least conceptually) your pentesting team was able to bypass freeRASP, I'm afraid we won't be able to determine how to prevent it right now. There may be multiple ways how to bypass appIntegrity; the attack may occur on multiple layers, e.g. in native iOS, JS, RN bridge...

Best,
Tomas from Talsec

@msikyna msikyna added the waiting for response Response from reporter is needed label Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for response Response from reporter is needed
Projects
None yet
Development

No branches or pull requests

3 participants