From: akuster808 <akuster808@gmail.com>
To: Sinan Kaya <okaya@kernel.org>, openembedded-core@lists.openembedded.org
Subject: Re: [sumo] [PATCH v1 2/2] libcroco: CVE-2017-7961
Date: Tue, 25 Sep 2018 16:16:00 -0700 [thread overview]
Message-ID: <17737fac-197f-65b9-0e84-e470c811be92@gmail.com> (raw)
In-Reply-To: <20180925171828.8655-2-okaya@kernel.org>
On 09/25/2018 10:18 AM, Sinan Kaya wrote:
> * CVE-2017-7961
> The cr_tknzr_parse_rgb function in cr-tknzr.c in libcroco has an
> "outside the range of representable values of 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 CSS file.
>
> CVE: CVE-2017-7961
> Ref: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-7961
> Signed-off-by: Sinan Kaya <okaya@kernel.org>
> ---
> .../libcroco/libcroco/CVE-2017-7961.patch | 45 +++++++++++++++++++
> .../libcroco/libcroco_0.6.12.bb | 2 +
> 2 files changed, 47 insertions(+)
> create mode 100644 meta/recipes-support/libcroco/libcroco/CVE-2017-7961.patch
>
> diff --git a/meta/recipes-support/libcroco/libcroco/CVE-2017-7961.patch b/meta/recipes-support/libcroco/libcroco/CVE-2017-7961.patch
> new file mode 100644
> index 0000000000..d407eca6d8
> --- /dev/null
> +++ b/meta/recipes-support/libcroco/libcroco/CVE-2017-7961.patch
> @@ -0,0 +1,45 @@
> +From 5fa3165613b77b516e2b0dc128f73b673bd3ec8b Mon Sep 17 00:00:00 2001
> +From: Ignacio Casal Quinteiro <qignacio@amazon.com>
> +Date: Sun, 16 Apr 2017 13:56:09 +0200
> +Subject: [PATCH] tknzr: support only max long rgb values
> +
> +This fixes a possible out of bound when reading rgbs which
> +are longer than the support MAXLONG
> +
> +Upstream-Status: Backport [https://git.gnome.org/browse/libcroco/patch/?id=9ad72875e9f08e4c519ef63d44cdbd94aa9504f7]
Please add;
CVE: CVE-2017-7961
> +Signed-off-by: Sinan Kaya <okaya@kernel.org>
> +---
> + src/cr-tknzr.c | 10 ++++++++++
> + 1 file changed, 10 insertions(+)
> +
> +diff --git a/src/cr-tknzr.c b/src/cr-tknzr.c
> +index e3af0ee..76886ec 100644
> +--- a/src/cr-tknzr.c
> ++++ b/src/cr-tknzr.c
> +@@ -1280,6 +1280,11 @@ cr_tknzr_parse_rgb (CRTknzr * a_this, CRRgb ** a_rgb)
> + status = cr_tknzr_parse_num (a_this, &num);
> + ENSURE_PARSING_COND ((status == CR_OK) && (num != NULL));
> +
> ++ if (num->val > G_MAXLONG) {
> ++ status = CR_PARSING_ERROR;
> ++ goto error;
> ++ }
> ++
> + red = num->val;
> + cr_num_destroy (num);
> + num = NULL;
> +@@ -1299,6 +1304,11 @@ cr_tknzr_parse_rgb (CRTknzr * a_this, CRRgb ** a_rgb)
> + status = cr_tknzr_parse_num (a_this, &num);
> + ENSURE_PARSING_COND ((status == CR_OK) && (num != NULL));
> +
> ++ if (num->val > G_MAXLONG) {
> ++ status = CR_PARSING_ERROR;
> ++ goto error;
> ++ }
> ++
> + PEEK_BYTE (a_this, 1, &next_bytes[0]);
> + if (next_bytes[0] == '%') {
> + SKIP_CHARS (a_this, 1);
> +--
> +2.19.0
> +
> diff --git a/meta/recipes-support/libcroco/libcroco_0.6.12.bb b/meta/recipes-support/libcroco/libcroco_0.6.12.bb
> index d86ddd6464..dd7dad424c 100644
> --- a/meta/recipes-support/libcroco/libcroco_0.6.12.bb
> +++ b/meta/recipes-support/libcroco/libcroco_0.6.12.bb
> @@ -16,5 +16,7 @@ BINCONFIG = "${bindir}/croco-0.6-config"
>
> inherit gnomebase gtk-doc binconfig-disabled
>
> +SRC_URI += "file://CVE-2017-7961.patch"
> +
> SRC_URI[archive.md5sum] = "bc0984fce078ba2ce29f9500c6b9ddce"
> SRC_URI[archive.sha256sum] = "ddc4b5546c9fb4280a5017e2707fbd4839034ed1aba5b7d4372212f34f84f860"
next prev parent reply other threads:[~2018-09-25 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 17:18 [sumo] [PATCH v1 1/2] libice: CVE-2017-2626 Sinan Kaya
2018-09-25 17:18 ` [sumo] [PATCH v1 2/2] libcroco: CVE-2017-7961 Sinan Kaya
2018-09-25 23:16 ` akuster808 [this message]
2018-09-25 23:15 ` [sumo] [PATCH v1 1/2] libice: CVE-2017-2626 akuster808
2018-09-27 1:15 ` akuster808
2018-09-27 1:21 ` Sinan Kaya
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=17737fac-197f-65b9-0e84-e470c811be92@gmail.com \
--to=akuster808@gmail.com \
--cc=okaya@kernel.org \
--cc=openembedded-core@lists.openembedded.org \
/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