Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: Shockwave 12.0.3.133

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:
CSI

This thread has been marked as locked.
ardengard Shockwave 12.0.3.133
Member 5th Sep, 2013 14:43
Ranking: 0
Posts: 3
User Since: 31st Jan, 2011
System Score: N/A
Location: SE
I have detected an issue with updating from Shockwave v10 to v12. The latest Shockwave-msi from Adobe not only installs version 12.0.3.133 but also files in System32\macromed\Shockwave 10. This means that CSI finds the SwInit.exe file, which has the version 10.4.1.44, in System32\macromed\Shockwave 10 and gives it the status of end-of-life. If you then distribute an updatepackages it will try to update it, which it shouldn't because it belongs to Shockwave 12.0.3.133.

This user no longer exists RE: Shockwave 12.0.3.133
Secunia Official 10th Sep, 2013 08:56
Hi,

The old version of Shockwave is indeed included within the 12.x release for backward compatibility. Secunia does detect the vulnerabilities in the file that belongs to version 10.x and lists them as it should be.

Whether you distribute an Update package to patch this particular version of Shockwave depends only on you. Should you want to avoid patching this version, you have to deselect the Applicability Path pointing to the Shockwave 10.x installation location from step 3 of the Secunia Package Wizard. Deselecting the path within the package makes the package you create _not_applicable_ to the system that would have Shockwave 10.x installed.

You could also create a blacklist under Scanning in CSI that will avoid scanning the location of Shockwave 10.x. Since this path was avoided, the CSI will not display this version within your scan results and so it will not include it as a target to-be-patched within a new Update package you created.

Please note that Secunia would not recommend you to patch this version either, however, to avoid patching it depends on your processes (scanning allowance / package configuration).

Kind regards / Stay Secure
Rosen Danailov / Security +
Secunia Customer Support

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer