Forum Thread: Shockwave Player

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
All Threads

This thread has been marked as locked.
Nikilet Shockwave Player
Member 28th Oct, 2009 08:25
Ranking: 7
Posts: 334
User Since: 15th Jul, 2008
System Score: N/A
Location: N/A
When I go to Add/Remove I have Adobe Shockwave Player 11.5 installed.

But psi tells me that I have two instances of Shockwave Player 10x that are end of life. I selected the download button and installed but rescan says there are no changes and it is still end of life.

The paths are:
C:\Windows\System32\Macromed\Shockwave 10\SwOnce.dll
C:\Windows\System32\Macromed\Shockwave 10\SwInit.exe

How do I handle this?

Maurice Joyce RE: Shockwave Player
Handling Contributor 28th Oct, 2009 09:00
Score: 12325
Posts: 9,575
User Since: 4th Jan 2009
System Score: N/A
Location: UK
Last edited on 28th Oct, 2009 09:02
More details on this subject are here:

http://secunia.com/community/forum/thread/show/287...

http://secunia.com/community/forum/thread/show/297...

I followed your posts on the BitDefender Forum. Looked like a false positive but unsure if the problem is history.

--
Maurice

Microsoft Surface 4 Intel i7 64Bit
Windows 10 Pro version 1809 Build 17763.404
16 GB RAM
IE & Edge Only
Was this reply relevant?
+0
-0
Nikilet RE: Shockwave Player
Member 28th Oct, 2009 15:10
Score: 7
Posts: 334
User Since: 15th Jul 2008
System Score: N/A
Location: N/A
First, the deal with BitDefender that you are referring to seems to be solved.

As to this Shockwave situation, I'm not sure what I was reading in the links you gave me. I thought one said that this is now a part of Shockwave 11 so just have psi ignore it. Then another seemed to say to uninstall. When these answers get too technical I am lost. So I still don't know what to do about this.
Was this reply relevant?
+0
-0
Maurice Joyce RE: Shockwave Player
Handling Contributor 28th Oct, 2009 16:51
Score: 12325
Posts: 9,575
User Since: 4th Jan 2009
System Score: N/A
Location: UK
I do not use Adobe free products but it looks like they have inserted somw elements of V10 into V11 for backward compatibility.

I would go with the Secunia advice & create an ignore rule.

--
Maurice

Microsoft Surface 4 Intel i7 64Bit
Windows 10 Pro version 1809 Build 17763.404
16 GB RAM
IE & Edge Only
Was this reply relevant?
+0
-0
Nikilet RE: Shockwave Player
Member 28th Oct, 2009 17:53
Score: 7
Posts: 334
User Since: 15th Jul 2008
System Score: N/A
Location: N/A
From various things I've read I wish I could get rid of Shockwave, but if I play games on my computer don't I have to have this?
Was this reply relevant?
+0
-0
Nikilet RE: Shockwave Player
Member 28th Oct, 2009 22:39
Score: 7
Posts: 334
User Since: 15th Jul 2008
System Score: N/A
Location: N/A
I posted in Adobe forum about this and following is their answer:

There is no threat from 10.4.1.26 and it is indeed a backward compatibilty player for pre-Unicode content. Tell whatever to ignore it - it's still in active development and 10.4.1.27 is on the verge of release

Now I have another question. I selected in psi to ignore these 2 items but the way the window read, now psi will not warn me of any other updates or anything required on this. Is that correct? Does this just refer to this Adobe Player 10x, or will this also apply to my Shockwave Player 11?
Was this reply relevant?
+0
-0
Maurice Joyce RE: Shockwave Player
Handling Contributor 29th Oct, 2009 11:37
Score: 12325
Posts: 9,575
User Since: 4th Jan 2009
System Score: N/A
Location: UK
As I am sure U are aware PSI scans all hard drives by default.

It will not publish any resulting insecurities from drives/folders/programmes chosen to ignore hence the caveat used by Secunia on ignore rules.

On that basis there is no warning after scanning if something ignored develops a further vulnerability.

There are two choices to ignore - the PSI Toolbox which points directly to the path or a Global Ignore via settings.

The alternate method is not to create an ignore rule - the alleged "vulnerability" will appear after each scan but is then notionally ignored given the user is aware of the issue.

--
Maurice

Microsoft Surface 4 Intel i7 64Bit
Windows 10 Pro version 1809 Build 17763.404
16 GB RAM
IE & Edge Only
Was this reply relevant?
+0
-0

This thread has been marked as locked.