From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] tiff: add upstream security fixes
Date: Fri, 28 Apr 2017 14:33:33 +0200 [thread overview]
Message-ID: <87lgqkhftu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170426215814.21533-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 26 Apr 2017 23:58:14 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Add upstream post-4.0.7 commits (except for ChangeLog modifications) fixing
> the following security issues:
> CVE-2016-10266 - LibTIFF 4.0.7 allows remote attackers to cause a denial of
> service (divide-by-zero error and application crash) via a crafted TIFF
> image, related to libtiff/tif_read.c:351:22.
> CVE-2016-10267 - LibTIFF 4.0.7 allows remote attackers to cause a denial of
> service (divide-by-zero error and application crash) via a crafted TIFF
> image, related to libtiff/tif_ojpeg.c:816:8.
> CVE-2016-10269 - LibTIFF 4.0.7 allows remote attackers to cause a denial of
> service (heap-based buffer over-read) or possibly have unspecified other
> impact via a crafted TIFF image, related to "READ of size 512" and
> libtiff/tif_unix.c:340:2.
> CVE-2016-10270 - LibTIFF 4.0.7 allows remote attackers to cause a denial of
> service (heap-based buffer over-read) or possibly have unspecified other
> impact via a crafted TIFF image, related to "READ of size 8" and
> libtiff/tif_read.c:523:22.
> CVE-2017-5225 - LibTIFF version 4.0.7 is vulnerable to a heap buffer
> overflow in the tools/tiffcp resulting in DoS or code execution via a
> crafted BitsPerSample value.
> CVE-2017-7592 - The putagreytile function in tif_getimage.c in LibTIFF 4.0.7
> has a left-shift undefined behavior issue, which might allow remote
> attackers to cause a denial of service (application crash) or possibly have
> unspecified other impact via a crafted image.
> CVE-2017-7593 - tif_read.c in LibTIFF 4.0.7 does not ensure that tif_rawdata
> is properly initialized, which might allow remote attackers to obtain
> sensitive information from process memory via a crafted image.
> CVE-2017-7594 - The OJPEGReadHeaderInfoSecTablesDcTable function in
> tif_ojpeg.c in LibTIFF 4.0.7 allows remote attackers to cause a denial of
> service (memory leak) via a crafted image.
> CVE-2017-7595 - The JPEGSetupEncode function in tiff_jpeg.c in LibTIFF 4.0.7
> allows remote attackers to cause a denial of service (divide-by-zero error
> and application crash) via a crafted image.
> CVE-2017-7598 - tif_dirread.c in LibTIFF 4.0.7 might allow remote attackers
> to cause a denial of service (divide-by-zero error and application crash)
> via a crafted image.
> CVE-2017-7601 - LibTIFF 4.0.7 has a "shift exponent too large for 64-bit
> type long" undefined behavior issue, which might allow remote attackers to
> cause a denial of service (application crash) or possibly have unspecified
> other impact via a crafted image.
> CVE-2017-7602 - LibTIFF 4.0.7 has a signed integer overflow, which might
> allow remote attackers to cause a denial of service (application crash) or
> possibly have unspecified other impact via a crafted image.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-04-28 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:58 [Buildroot] [PATCH] tiff: add upstream security fixes Peter Korsgaard
2017-04-27 12:13 ` Peter Korsgaard
2017-04-28 12:33 ` Peter Korsgaard [this message]
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=87lgqkhftu.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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