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
We have got a report from a security researcher, who pointed out that Capacitor by default logs full file content of a file that is saved via its Filesystem plugin. E.g we call Filesystem.writeFile in our code, saving state.json (which is a Redux state).
Full content of the saved file is then visible in Android logs via logcat, example/screenshot:
Providing a second screenshot where it's seen that it is logged not "from the Filesystem plugin code", but from some generic code that logs generic Plugin input/output (possibly in the V verbose level):
Expected Behavior
We expect to be able to disable this automatic logging functionality via some flag/setting, as it can leak some PII/sensitive data to someone who has access to logcat.
The text was updated successfully, but these errors were encountered:
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Capacitor, please create a new issue and ensure the template is fully filled out.
Bug Report
Capacitor Version
Platform(s)
Android
Current Behavior
We have got a report from a security researcher, who pointed out that Capacitor by default logs full file content of a file that is saved via its Filesystem plugin. E.g we call
Filesystem.writeFile
in our code, savingstate.json
(which is a Redux state).Full content of the saved file is then visible in Android logs via
logcat
, example/screenshot:Providing a second screenshot where it's seen that it is logged not "from the Filesystem plugin code", but from some generic code that logs generic Plugin input/output (possibly in the
V
verbose level):Expected Behavior
We expect to be able to disable this automatic logging functionality via some flag/setting, as it can leak some PII/sensitive data to someone who has access to
logcat
.The text was updated successfully, but these errors were encountered: