• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Urgent Problem with Adobe Flash Player and Flash Player Debugger 31.0.0.148 - New Security Custom Definitions

New Here ,
Nov 16, 2018 Nov 16, 2018

Copy link to clipboard

Copied

Hello,

My colleagues who are managing the security updates are facing the following issue, could you please explain to us how to solve it

Thank you

We query their update server using the following URL:

http://fpdownload2.macromedia.com/pub/flashplayer/update/current/sau/currentmajor.xml

The answer look like this:

<version>

<Player major="31" majorBeta="31"/>

</version>

It allows to determine the current major version which is used to determine the next URL:

http://fpdownload2.macromedia.com/pub/flashplayer/update/current/sau/31/xml/version.xml

The answer contains all the current versions and  look like this:

<version>

<ActiveX major="31" minor="0" buildMajor="0" buildMinor="148"/>

<Plugin major="31" minor="0" buildMajor="0" buildMinor="148"/>

<Pepper major="31" minor="0" buildMajor="0" buildMinor="148"/>

<MacPlugin major="31" minor="0" buildMajor="0" buildMinor="148"/>

<MacPepper major="31" minor="0" buildMajor="0" buildMinor="148"/>

<SAUConfig checkFrequency="1"/>

</version>

So here is a little history of the versions served by their server:

  • 13/11/2018 6:00AM: 31.0.0.122.
  • 14/11/2018 6:00AM: 31.0.0.148.
  • 15/11/2018 6:00AM: 31.0.0.148.
  • 16/11/2018 6:00AM: 31.0.0.122.
  • 16/11/2018 09:59AM: 31.0.0.148.

So somewhere between 15/11/2018 6:00AM and today 6:00AM a rollback to 31.0.0.122 has occurred.

When we noticed this we checked again at 9H59AM and 31.0.0.148 was available again.

Views

504

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Nov 16, 2018 Nov 16, 2018

I reviewed the deployed files and do not see where this would have occurred at 6:00 am on Nov 16.  The last time the version.xml file was updated was on November 13 when version 31.0.0.148 was released. I don't see it being reverted to version 31.0.0.122 after it was updated to version 31.0.0.148.

Also, it is not recommended to use the version.xml file to query for a new version of Flash Player.  It is recommended to use https://fpdownload.macromedia.com/pub/flashplayer/masterversion/masterversion.xml

...

Votes

Translate

Translate
Adobe Employee ,
Nov 16, 2018 Nov 16, 2018

Copy link to clipboard

Copied

I reviewed the deployed files and do not see where this would have occurred at 6:00 am on Nov 16.  The last time the version.xml file was updated was on November 13 when version 31.0.0.148 was released. I don't see it being reverted to version 31.0.0.122 after it was updated to version 31.0.0.148.

Also, it is not recommended to use the version.xml file to query for a new version of Flash Player.  It is recommended to use https://fpdownload.macromedia.com/pub/flashplayer/masterversion/masterversion.xml instead.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 21, 2018 Nov 21, 2018

Copy link to clipboard

Copied

LATEST

Thank you

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines