Skip to main content
Legend
October 27, 2021

P: Photoshop 23.0 - cannot open TIF files, generated in other programs

  • October 27, 2021
  • 155 replies
  • 61982 views

Starting from version 22.5.2 Photoshop stopped opening some tif files. The issue is related to a previously discovered vulnerability, the escalation of which, under certain conditions, may lead to arbitrary code execution - Adobe Security Bulletin.

 

Important: The problem is not with Photoshop, but with third-party software developers who do not keep track of current TIF specifications

 

A temporary solution to the problem is to convert files in third-party editors that completely update the structure of TIF files (for example, xnView, ImageMagik, etc.); such files can also be converted using the Camera Raw plug-in (via Bridge).

We all hope that Adobe can solve this problem and find a way to bring third-party files to modern standard. But I recommend that you independently contact the developers of programs whose files Photoshop cannot open. Notify them of the problem, recommend to contact @J453 using this community. Jeffrey can provide technical information to developers to solve this problem.

List of apps that have problems (according to your feedback):

 

There are no problems (or solved):

 

This topic has been closed for replies.

155 replies

Participant
December 14, 2021

Thanks for the update. Will there also be a 23.0.3 build with this TIF change?

Jan Lunddal Larsen-PRIVAT
Participant
December 14, 2021

It seems to have fixed our problems with images created from Imagemagick and Apple Preview 🙂

Mohit Goyal
Community Manager
Community Manager
December 14, 2021

Hi all,  

 

We're happy to announce the release of Photoshop 23.1. This update includes the fix for this issue. To see the list of all fixed issues, click here

To update Photoshop to 23.1, click "Update" in the Creative Cloud desktop app next to Photoshop. More detailed instructions for updating  

 

Let us know if the update resolves the problem for those affected and share your feedback with us.

 

Thanks,

Mohit

Participant
December 9, 2021

Hi Jeff, what about tiled TIFFs? It seems that the new Photoshop rejects our tiled tiffs for the very same reason: because of the missing RowsPerStrip (278) entry? To my understanding it is not intended to write tiled tiffs with the RowsPerStrip (278) entry. What can we do about that?

Legend
December 4, 2021

@Stellar_gift16B8 Feel free to post or DM me a link to a Tiled TIFF from your workflow so I can have engineering regress any changes with it.

Stellar_gift16B8
Participant
December 3, 2021

@J453 Please do. Tiled Tiff files seem to be the cause of the error with all the existing files I have produced from Ultramap. Outputting files as scanline/interleaved, versus tiled/interleaved, resolves the file opening error. I have set all of my outputs as tiled, until now, since my orthophoto software requires tiled tifs and converts them before they can be imported.

Legend
December 2, 2021

We are looking at one more flavor of TIFF (tiled) to allow/support.

Legend
December 2, 2021

@Barry Rudick If you're running 23.0.1 or later, Photoshop will reject TIFFs that lacked an attribute which could pose a security risk.

Inspiring
December 2, 2021

Responding to Jeff's post:

 

That seems like the likely plan to follow.

 

It is interesting that opening and closing takes care of the problem. But I assume that PS would see an "infected" TIFF and not allow it's use?

 

Should all incoming TIFF files (we are a fine art printng company) be suspect? Is there a sniffer program to check?

 

Thanks for the info.

Legend
December 2, 2021

To be clear, this is a security issue, not a "restrictive TIFF specification." TIFF is actually very open and has lot of flexibility but applications which don't follow a standard are always at the risk of being hijacked by exploits, and those are hard to fix after the fact.

Since TIFF is open, I would expect that image processing developers and image libraries will all incorporate some kind of fix in the future, but you may just be out of luck with an older and unsupported app. This is one valid argument put forth by those in the Free Software movement.

Now that the exploit is public, don't be surprised to see files floating around which could be a security risk.