Photoshop CS5 Users warning

May be of interest to one or two, here.

Thanks for the info and link. I was not aware of this issue.

I wonder what does happen if you open a boobytrapped .tif file and how would one recognise one?

John

It makes me wonder where we would pick up such a file and try to open it in CS5. Our own images won't be a problem and I never receive any TIFFs that I would want to open.

Some people like to download other user's posted images and show off their PS skills by posting "here's what I did with you photo". Booby trapping a badly PS'ed image might be a good way to discourage some show offs from messing with your images without asking - if you were so inclined.

Surefly though if they were posted they would be JPEGs or GIFs? We don't post TIFFs to the web.

We send and receive lots of tiff's at work via the drawing office. Any old drawing that predates the CAD systems are scanned as tiff's and embedded into an autocad dwg as a separate layer. Very often these drawings will be updated by other engineering teams outside of our company.

The CS Suite is installed on all the drawing office machines so I appreciate the 'heads up'.

I realise this different to how many people may use Photoshop but there are several valid reasons to why you may receive a tiff from a 3rd party as Adobe CS suite isn't just aimed at photographers.

Surely the AV software should pick up the Tiff's even if it
can't detect the damage done after it's been run?

It possibly should but I think you should really think of your AV as the last line of defence rather than relying on it to keep you safe.

A quick look at our software inventory suggests all our machines have been upgraded to later versions of the CS suite.

Also US-Cert Security Bulletin suggests this also affects Photoshop 5.5 which is different to what the Register article at the top states.

There were a lot of negative comments on the PS forum when Adobe announced the ‘fix’ was to upgrade to CS 6.0 – but since then Adobe have had a change of heart and announced a fix will be made available soon for CS5.5, I’m not sure about CS5.0