From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/7] libxslt: fix CVE-2019-18197
Date: Sun, 10 Nov 2019 22:54:10 +0800 [thread overview]
Message-ID: <20191110145416.5171-2-anuj.mittal@intel.com> (raw)
In-Reply-To: <20191110145416.5171-1-anuj.mittal@intel.com>
From: Joe Slater <joe.slater@windriver.com>
Use patch from upstream after 1.1.33 release.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
.../libxslt/files/CVE-2019-18197.patch | 33 +++++++++++++++++++
.../recipes-support/libxslt/libxslt_1.1.33.bb | 1 +
2 files changed, 34 insertions(+)
create mode 100644 meta/recipes-support/libxslt/files/CVE-2019-18197.patch
diff --git a/meta/recipes-support/libxslt/files/CVE-2019-18197.patch b/meta/recipes-support/libxslt/files/CVE-2019-18197.patch
new file mode 100644
index 0000000000..5f2b620396
--- /dev/null
+++ b/meta/recipes-support/libxslt/files/CVE-2019-18197.patch
@@ -0,0 +1,33 @@
+libxslt: fix CVE-2019-18197
+
+Added after 1.1.33 release.
+
+CVE: CVE-2019-18197
+Upstream-Status: Backport [https://gitlab.gnome.org/GNOME/libxslt.git]
+Signed-off-by: Joe Slater <joe.slater@windriver.com>
+
+commit 2232473733b7313d67de8836ea3b29eec6e8e285
+Author: Nick Wellnhofer <wellnhofer@aevum.de>
+Date: Sat Aug 17 16:51:53 2019 +0200
+
+ Fix dangling pointer in xsltCopyText
+
+ xsltCopyText didn't reset ctxt->lasttext in some cases which could
+ lead to various memory errors in relation with CDATA sections in input
+ documents.
+
+ Found by OSS-Fuzz.
+
+diff --git a/libxslt/transform.c b/libxslt/transform.c
+index 95ebd07..d7ab0b6 100644
+--- a/libxslt/transform.c
++++ b/libxslt/transform.c
+@@ -1094,6 +1094,8 @@ xsltCopyText(xsltTransformContextPtr ctxt, xmlNodePtr target,
+ if ((copy->content = xmlStrdup(cur->content)) == NULL)
+ return NULL;
+ }
++
++ ctxt->lasttext = NULL;
+ } else {
+ /*
+ * normal processing. keep counters to extend the text node
diff --git a/meta/recipes-support/libxslt/libxslt_1.1.33.bb b/meta/recipes-support/libxslt/libxslt_1.1.33.bb
index abc00a09ea..9f268e7bb0 100644
--- a/meta/recipes-support/libxslt/libxslt_1.1.33.bb
+++ b/meta/recipes-support/libxslt/libxslt_1.1.33.bb
@@ -12,6 +12,7 @@ SRC_URI = "http://xmlsoft.org/sources/libxslt-${PV}.tar.gz \
file://0001-Fix-security-framework-bypass.patch \
file://CVE-2019-13117.patch \
file://CVE-2019-13118.patch \
+ file://CVE-2019-18197.patch \
"
SRC_URI[md5sum] = "b3bd254a03e46d58f8ad1e4559cd2c2f"
--
2.21.0
next prev parent reply other threads:[~2019-11-10 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 14:54 [PATCH 0/7] Consolidated zeus pull request Anuj Mittal
2019-11-10 14:54 ` Anuj Mittal [this message]
2019-11-10 14:54 ` [PATCH 2/7] python3: Upgrade 3.7.4 -> 3.7.5 Anuj Mittal
2019-11-10 14:54 ` [PATCH 3/7] libpng: whitelist CVE-2019-17371 Anuj Mittal
2019-11-10 14:54 ` [PATCH 4/7] procps: whitelist CVE-2018-1121 Anuj Mittal
2019-11-10 14:54 ` [PATCH 5/7] libsndfile1: whitelist CVE-2018-13419 Anuj Mittal
2019-11-10 14:54 ` [PATCH 6/7] libpam: set CVE_PRODUCT Anuj Mittal
2019-11-10 14:54 ` [PATCH 7/7] libgcrypt: fix CVE-2019-13627 Anuj Mittal
2019-11-10 15:02 ` ✗ patchtest: failure for Consolidated zeus pull request Patchwork
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=20191110145416.5171-2-anuj.mittal@intel.com \
--to=anuj.mittal@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.