Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Shockwave Player shown as vulnerable but updated 3X & Flash Player up to date.

  • 1 reply
  • 2 have this problem
  • 21 views
  • Last reply by teeter

teeter
teeter
more options

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter

Plugin Status loaded in Firefox. It showed both Adobe Flash Player and Adobe Shockwave Player as vulnerable. Updating Adobe Flasy Player to Shockwave Flash 22.0.0.292 seemed to work and show it uptodate but Adobe Shockwave Player remained vulnerable. I keep going to the link to update Adobe Shockwave Player, but after I do I still get the vulnerable designation (after refreshing). I have tried to uninstall and reinstall. I have restarted Firefox, although it doesn't say I need to. I'm wondering if this is a problem that Adobe changed the name. Or that the two are synonymous now. Martha Teeter
Attached screenshots

All Replies (1)

teeter
teeter Question owner
more options

I meant 22.0.0.192. Well in looking for support, I refreshed Firefox. And now the problem seems to have disappeared. No vulnerable Adobe Shockwave Flash.