Skip to contentSkip to conversation

python/python3: Whitelist CVE-2019-18348

PATCH Superseded Adrian Bunk 2 participants 2 messages Dec 6, 2019

v2 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 python/python3: Whitelist CVE-2019-18348

This is not exploitable when glibc has CVE-2016-10739 fixed, which is fixed in the upstream version since warrior.

---
 meta/recipes-devtools/python/python.inc       | 3 +++
 meta/recipes-devtools/python/python3_3.8.0.bb | 3 +++
 2 files changed, 6 insertions(+)
meta/recipes-devtools/python/python.inc +3 -0
index 110ec315d9..19a2f3e743 100644
@@ -29,6 +29,9 @@ CVE_CHECK_WHITELIST += "CVE-2017-18207"
 # of Python that cannot really be altered at this point."
 CVE_CHECK_WHITELIST += "CVE-2015-5652"
 
+# This is not exploitable when glibc has CVE-2016-10739 fixed.
+CVE_CHECK_WHITELIST += "CVE-2019-18348"
+
 PYTHON_MAJMIN = "2.7"
 
 inherit autotools pkgconfig
meta/recipes-devtools/python/python3_3.8.0.bb +3 -0
index 1feaebea8e..92f6527c70 100644
@@ -42,6 +42,9 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
 
 CVE_PRODUCT = "python"
 
+# This is not exploitable when glibc has CVE-2016-10739 fixed.
+CVE_CHECK_WHITELIST += "CVE-2019-18348"
+
 PYTHON_MAJMIN = "3.8"
 
 S = "${WORKDIR}/Python-${PV}"
Signature · 1 line
2.17.1
#1 lore raw

✗ patchtest: failure for python/python3: Whitelist CVE-2019-18348

== Series Details ==

Series: python/python3: Whitelist CVE-2019-18348
Revision: 1
URL : https://patchwork.openembedded.org/series/21497/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at d40853b10d)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe