Bug 2112 - tag name handling with TIFFMergeFieldInfo()
: tag name handling with TIFFMergeFieldInfo()
Status: RESOLVED LATER
: libtiff
default
: unspecified
: Other NetBSD
: P2 normal
: ---
Assigned To:
:
:
: migrated_to_gitlab
:
:
  Show dependency treegraph
 
Reported: 2009-10-29 07:34 by
Modified: 2019-10-01 14:19 (History)


Attachments
sample code that crashes when tag names are changed to "Tag %d" (1.22 KB, text/plain)
2009-10-29 07:34, Juergen Buchmueller
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-10-29 07:34:46
Created an attachment (id=346) [details]
sample code that crashes when tag names are changed to "Tag %d"

When a client application uses the same names for its tags as libtiff itself
would use in the Default Tag Auto-registration - that is "Tag %d" with
field_tag as number - the lib will SIGSEGV on TIFFClose().

Possible solution: Make TIFFMergeFieldInfo() return an int that indicates if
the passed array is acceptable or not and reject field names that collide with
internal names.

Otherwise find the code that relies on the field name to do something
internally that should not be done if the field name was defined by a client
application.
------- Comment #1 From 2019-10-01 14:19:20 -------
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets,
such as this one, have been migrated to the libtiff GitLab instance at
https://gitlab.com/libtiff/libtiff/issues .

The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is
the initial Bugzilla issue number.