Google Play security warning

7317
12
Jump to solution
06-16-2016 10:45 AM
BrianHovis
Occasional Contributor II

I received the following message today from Google Play.  I assume that the file to which they refer is part of the template.  I know you are making updates, so perhaps this is already included.

Hello Google Play Developer,

We detected that your app(s) listed at the end of this email are using an unsafe version of the libpng library. Apps with vulnerabilities like this can expose users to risk of compromise and may be considered in violation of our Malicious Behavior policy.

What’s happening

Beginning September 17, 2016, Google Play will block publishing of any new apps or updates that use vulnerable versions of libpng. Your published APK version will not be affected, however any updates to the app will be blocked unless you address this vulnerability.

Action required: Migrate your app(s) to use libpng v1.0.66, v.1.2.56, v.1.4.19, v1.5.26 or higher as soon as possible and increment the version number of the upgraded APK.

Next steps

  1. Download the latest version of libpng from the libpng website.
  2. Sign in to your Developer Console and submit the updated version of your app.
  3. Check back after five hours - we’ll show a warning message if the app hasn’t been updated correctly.

The vulnerability stems from an out of bounds memory access that could potentially lead to code execution. Versions 1.0.x before 1.0.66, 1.1.x and 1.2.x before 1.2.56, 1.3.x and 1.4.x before 1.4.19, and 1.5.x before 1.5.26 are affected.

You can read more about the vulnerability in CVE-2015-8540. For other technical questions about the vulnerability, you can post to Stack Overflow and use the tag “android-security.”

While these specific issues may not affect every app that uses libpng, it’s best to stay up to date on all security patches.

We’re here to help

If you feel we have sent this warning in error, you can contact our developer support team.

Regards,

The Google Play Team

Affected app(s) and version(s) are listed below. If you have more than 20 affected apps in your account, please check the Developer Console for a full list.

com.esri.appdede77e19d354ae09a093d94937a760e   1000006

12 Replies
nakulmanocha
Esri Regular Contributor

It is supposed to show up on the Esri Support Home page. Unfortunately, it is not public yet. But rest assured the team is working on it to get it fixed.

0 Kudos
AkhilSharma
New Contributor
0 Kudos
MarikaVertzonis
Esri Regular Contributor

The runtime fix has now been applied to the AppStudio cloud Make service. You do not need to install a new version of AppStudio to make use of this fix - just build your app again with cloud Make.