Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

current Shockwave Flash player file incorrectly labeled, how fix?

  • 6 antwoorde
  • 5 hierdie probleem
  • 20 views
  • Laaste antwoord deur bobv

more options

The current Shockwave flash player plugin for Firefox:

NPSWF32_16_0_0_296.dll

is labeled in file Properties as:

Shockwave Flash 16.0 r0


This is causing Firefox to think it is not a current version, vulnerable, and thus firefox is blocking it.

We need Adobe to correctly label the file properties and make that correctly labeled file available for download. How do we get that done???

Note that the "installed" shockwave flash player shows 16.0r0, but it's really 6_0_0_296.

The current Shockwave flash player plugin for Firefox: NPSWF32_16_0_0_296.dll is labeled in file Properties as: Shockwave Flash 16.0 r0 This is causing Firefox to think it is not a current version, vulnerable, and thus firefox is blocking it. We need Adobe to correctly label the file properties and make that correctly labeled file available for download. How do we get that done??? Note that the "installed" shockwave flash player shows 16.0r0, but it's really 6_0_0_296.

All Replies (6)

more options

Actually the Flash player 16.0.0.296 for Windows/Mac is considered vulnerable as of today however Adobe does not have an update yet.

https://helpx.adobe.com/security/products/flash-player/apsa15-02.html

The update will be at https://www.adobe.com/products/flashplayer/distribution3.html when it is available.

more options

So it sure would help if they had their current file correctly labeled so we could at least use it. I'm going to assume it's better than 16.0r0. I appreciate the information, but it does not solve the problem.

more options

Try to delete the pluginreg.dat file in the Firefox Profile Folder and maybe addons.sqlite as well to reset the plugin registry databases.

See Re-initializing the plugins database:

more options

So James, you left out a couple of critical pieces of info: 1. The defect is considered CRITICAL by Adobe and is being exploited in the field. 2. They expect to have an updated file this week. It's good that FF is keeping us away from this potential issue. However I still think Adobe needs to label their files correctly!

To cor-el: IF the problem is that FF is pulling the version from the FILE DESCRIPTION field, then what you suggest won't help. Its still going to come back wrong. (but I'll try it  :))

more options

I did not mention that since I gave the link for the same information.

more options

cor-el tried your suggestion. no change. still sees the file version as 16.0r0 i could not find a file called "addons.sqlite" Thanks.