From: "Yaakov S (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: SECURITY: tiff
Date: Thu, 13 Jul 2006 01:07:00 -0000 [thread overview]
Message-ID: <44B59CB8.4010401@users.sourceforge.net> (raw)
In-Reply-To: <44907C27.3010608@users.sourceforge.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
>>> Multiple vulnerabilities, ranging from integer overflows and NULL
>>> pointer dereferences to double frees, were reported in libTIFF.
And now, there's more:
A buffer overflow has been found in the t2p_write_pdf_string function in
tiff2pdf, which can been triggered with a TIFF file containing a
DocumentName tag with UTF-8 characters. An additional buffer overflow
has been found in the handling of the parameters in tiffsplit.
Solution: update to 3.8.2 and apply the following patches:
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/media-libs/tiff/files/tiff-3.8.2-tiffsplit.patch
http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/media-libs/tiff/files/tiff-buffer.patch
More information:
http://www.gentoo.org/security/en/glsa/glsa-200607-03.xml
http://bugs.gentoo.org/show_bug.cgi?id=135021
http://bugs.gentoo.org/show_bug.cgi?id=135881
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2193
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2656
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEtZy4piWmPGlmQSMRAo2pAJ9gEq6uMHL4j7TvhGHL+j8RyN9Y+ACcCczX
PzQldn5/cuh2WwiUn9ifBF0=
=Cztp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-07-13 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 22:26 Yaakov S (Cygwin Ports)
2006-06-14 21:14 ` Yaakov S (Cygwin Ports)
2006-07-13 1:07 ` Yaakov S (Cygwin Ports) [this message]
2006-07-13 1:10 ` Yaakov S (Cygwin Ports)
2006-07-19 21:34 ` Yaakov S (Cygwin Ports)
2011-04-03 20:17 Yaakov (Cygwin/X)
2011-04-04 14:20 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44B59CB8.4010401@users.sourceforge.net \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).