TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Expanding the Attack Surface: React Native Android Applications

37 点作者 infosecau超过 5 年前

5 条评论

axemclion超过 5 年前
I am not sure if this is specific to React Native. In a regular Android application, this information is available in the JSON file. Having permissive credentials on the client is a security gap, no matter the technology.
maury91超过 5 年前
This article highlights some security errors that are not really related to React Native:<p>1. Firebase permissions<p>That is a problem of a badly configured server, in firebase you need to write some rules that are less permissive as possible, making possible only to read what the user really needs (for example it&#x27;s own data and the data that is truly public), same for writing.<p>2. Debug files in the APK<p>The map file should not be in the APK (unless it&#x27;s an internal-only debuggable APK), webpack&#x2F;gulp can be configured to not produce that file when the target is production.<p>If you use tools that collect errors like Sentry, you can upload the map file to their servers and avoid releasing it.<p>It will not stop the attacker from obtaining your API_KEY but it will make it harder (security through obscurity).<p>Both problems are not exclusive to React Native but are shared to any app&#x2F;web-app that uses firebase.
secondo超过 5 年前
To the author, your blog platform outputs an invalid canonical url for your content. It omits the `blog` subdomain which makes your canonical url point to a 404.
评论 #22221752 未加载
merrvk超过 5 年前
Isn&#x27;t this just security 101? Not sure what it has to do with React Native
reilly3000超过 5 年前
Do people really put server keys into clients? I thought the general assumption outside of private servers is to trust nobody.
评论 #22221851 未加载