1# This file contains a list of CVE's where resolution has proven to be impractical 2# or there is no reasonable action the Yocto Project can take to resolve the issue. 3# It contains all the information we are aware of about an issue and analysis about 4# why we believe it can't be fixed/handled. Additional information is welcome through 5# patches to the file. 6# 7# Include this file in your local.conf or distro.conf to exclude these CVE's 8# from the cve-check results or add to the bitbake command with: 9# -R conf/distro/include/cve-extra-exclusions.inc 10# 11# The file is not included by default since users should review this data to ensure 12# it matches their expectations and usage of the project. 13# 14# We may also include "in-flight" information about current/ongoing CVE work with 15# the aim of sharing that work and ensuring we don't duplicate it. 16# 17 18# strace https://nvd.nist.gov/vuln/detail/CVE-2000-0006 19CVE_STATUS[CVE-2000-0006] = "upstream-wontfix: CVE is more than 20 years old \ 20with no resolution evident. Broken links in CVE database references make resolution impractical." 21 22# epiphany https://nvd.nist.gov/vuln/detail/CVE-2005-0238 23CVE_STATUS[CVE-2005-0238] = "upstream-wontfix: \ 24The issue here is spoofing of domain names using characters from other character sets. \ 25There has been much discussion amongst the epiphany and webkit developers and \ 26whilst there are improvements about how domains are handled and displayed to the user \ 27there is unlikely ever to be a single fix to webkit or epiphany which addresses this \ 28problem. There isn't any mitigation or fix or way to progress this further." 29 30# glibc https://nvd.nist.gov/vuln/detail/CVE-2010-4756 31CVE_STATUS[CVE-2010-4756] = "upstream-wontfix: \ 32Issue is memory exhaustion via glob() calls, e.g. from within an ftp server \ 33Best discussion in https://bugzilla.redhat.com/show_bug.cgi?id=681681 \ 34Upstream don't see it as a security issue, ftp servers shouldn't be passing \ 35this to libc glob. Upstream have no plans to add BSD's GLOB_LIMIT or similar." 36 37# go https://nvd.nist.gov/vuln/detail/CVE-2020-29509 38# go https://nvd.nist.gov/vuln/detail/CVE-2020-29511 39CVE_STATUS_GROUPS += "CVE_STATUS_GO" 40CVE_STATUS_GO = "CVE-2020-29509 CVE-2020-29511" 41CVE_STATUS_GO[status] = "not-applicable-config: \ 42The encoding/xml package in go can potentially be used for security exploits if not used correctly \ 43CVE applies to a netapp product as well as flagging a general issue. We don't ship anything \ 44exposing this interface in an exploitable way" 45 46# db 47CVE_STATUS_GROUPS += "CVE_STATUS_DB" 48CVE_STATUS_DB = "CVE-2015-2583 CVE-2015-2624 CVE-2015-2626 CVE-2015-2640 CVE-2015-2654 \ 49CVE-2015-2656 CVE-2015-4754 CVE-2015-4764 CVE-2015-4774 CVE-2015-4775 CVE-2015-4776 CVE-2015-4777 \ 50CVE-2015-4778 CVE-2015-4779 CVE-2015-4780 CVE-2015-4781 CVE-2015-4782 CVE-2015-4783 CVE-2015-4784 \ 51CVE-2015-4785 CVE-2015-4786 CVE-2015-4787 CVE-2015-4788 CVE-2015-4789 CVE-2015-4790 CVE-2016-0682 \ 52CVE-2016-0689 CVE-2016-0692 CVE-2016-0694 CVE-2016-3418 CVE-2020-2981" 53CVE_STATUS_DB[status] = "upstream-wontfix: Since Oracle relicensed bdb, the open source community is slowly but surely \ 54replacing bdb with supported and open source friendly alternatives. As a result this CVE is unlikely to ever be fixed." 55 56# Kernel CVEs that are generic but can't be added to the kernel's hand-maintained cve-exclusion.inc 57# or machine-maintained cve-exclusion_VERSION.inc files, such as issues that describe TCP/IP design 58# flaws or processor-specific exploits that can't be mitigated. 59# 60# For OE-Core our policy is to stay as close to the kernel stable releases as we can. This should 61# ensure the bulk of the major kernel CVEs are fixed and we don't dive into each individual issue 62# as the stable maintainers are much more able to do that. 63CVE_STATUS[CVE-1999-0524] = "ignored: issue is that ICMP exists, can be filewalled if required" 64CVE_STATUS[CVE-2008-4609] = "ignored: describes design flaws in TCP" 65CVE_STATUS[CVE-2010-4563] = "ignored: low impact, only enables detection of hosts which are sniffing network traffic" 66CVE_STATUS[CVE-2011-0640] = "ignored: requires physical access and any mitigation would mean USB is impractical to use" 67 68# qemu:qemu-native:qemu-system-native https://nvd.nist.gov/vuln/detail/CVE-2021-20255 69CVE_STATUS[CVE-2021-20255] = "upstream-wontfix: \ 70There was a proposed patch https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06098.html \ 71qemu maintainers say the patch is incorrect and should not be applied \ 72The issue is of low impact, at worst sitting in an infinite loop rather than exploitable." 73 74# qemu:qemu-native:qemu-system-native https://nvd.nist.gov/vuln/detail/CVE-2019-12067 75CVE_STATUS[CVE-2019-12067] = "upstream-wontfix: \ 76There was a proposed patch but rejected by upstream qemu. It is unclear if the issue can \ 77still be reproduced or where exactly any bug is. \ 78We'll pick up any fix when upstream accepts one." 79 80# nasm:nasm-native https://nvd.nist.gov/vuln/detail/CVE-2020-18974 81CVE_STATUS[CVE-2020-18974] = "upstream-wontfix: \ 82It is a fuzzing related buffer overflow. It is of low impact since most devices \ 83wouldn't expose an assembler. The upstream is inactive and there is little to be \ 84done about the bug, ignore from an OE perspective." 85