dnsmasq: CVE-2017-15107
PATCH 1/1 dnsmasq: CVE-2017-15107
* CVE-2017-15107
A vulnerability was found in Dnsmasq's implementation of DNSSEC. Wildcard synthesized NSEC records could be improperly interpreted to prove the non-existence of hostnames that actually exist.
Affects dnsmasq <= 2.78
CVE: CVE-2017-15107
Ref: https://access.redhat.com/security/cve/cve-2017-15107
--- .../recipes-support/dnsmasq/dnsmasq_2.78.bb | 1 + .../dnsmasq/files/CVE-2017-15107.patch | 262 ++++++++++++++++++ 2 files changed, 263 insertions(+) create mode 100644 meta-networking/recipes-support/dnsmasq/files/CVE-2017-15107.patch
meta-networking/recipes-support/dnsmasq/dnsmasq_2.78.bb +1 -0
@@ -2,6 +2,7 @@ require dnsmasq.inc SRC_URI += "\ file://lua.patch \ + file://CVE-2017-15107.patch \ " SRC_URI[dnsmasq-2.78.md5sum] = "3bb97f264c73853f802bf70610150788"
meta-networking/recipes-support/dnsmasq/files/CVE-2017-15107.patch new file +262 -0
262 lines not on this page · raw message
Signature · 1 line
2.19.0
✗ patchtest: failure for dnsmasq: CVE-2017-15107
== Series Details ==
Series: dnsmasq: CVE-2017-15107
Revision: 1
URL : https://patchwork.openembedded.org/series/14200/
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 sent to the wrong mailing list or some patches from the series correspond to different mailing lists [test_target_mailing_list]
Suggested fix Send the series again to the correct mailing list (ML) Suggested ML [email protected] [http://git.openembedded.org/meta-openembedded/] Patch's path: meta-networking/recipes-support/dnsmasq/dnsmasq_2.78.bb
* 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 sumo (currently at 82b0189567)
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