-
Notifications
You must be signed in to change notification settings - Fork 374
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
[Bug]: Remote Webview debugging is enabled. #1488
Comments
Has this issue been added to the project road map? any approximation date on when this will be addressed? |
Any new about this? |
I apologize we do not have news yet, but we appreciate the bump! We will investigate |
Any new? |
A pentest of our app revealed that Remote WebView debugging is activated. This was specifically found in OneSignal: Any news about the issue yet? |
seems like that is false positive, because of this, if you do not set logLevel to debug and higher it should be OK |
I am having similar issue with Onesignal Android SDK with version 5.1.7. how can we disable Remote WEBview debugging? |
Hi, thanks for reaching out, |
@nan-li I have set this variable as you mentioned, but the issue persists. Another thing, during a scan I conducted on my APK, I found several paths or files containing the word "debug". Could you please help me clarify these points? |
Hi @Monfallet, a static analysis will pick up the existence of code, not whether the code is activated. The remote webview will only be set up if you use levels DEBUG or higher (so
|
What happened?
How can this Webview debugging mode be turned off?
I've included my release apk build in the Mobsf testing procedure to look for security flaws. Additionally, I received one serious problem from the Mobsf report for your package library. The screenshot for that report is attached. Please take action to fix the security problem.
Thank you.
Steps to reproduce?
What did you expect to happen?
I want to disable or remove that debugging line from the npm package code.
React Native OneSignal SDK version
Release 4.5.0
Which platform(s) are affected?
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: