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 19# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 20# CVE is more than 20 years old with no resolution evident 21# broken links in CVE database references make resolution impractical 22CVE_CHECK_IGNORE += "CVE-2000-0006" 23 24# epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-0238 25# The issue here is spoofing of domain names using characters from other character sets. 26# There has been much discussion amongst the epiphany and webkit developers and 27# whilst there are improvements about how domains are handled and displayed to the user 28# there is unlikely ever to be a single fix to webkit or epiphany which addresses this 29# problem. Ignore this CVE as there isn't any mitigation or fix or way to progress this further 30# we can seem to take. 31CVE_CHECK_IGNORE += "CVE-2005-0238" 32 33# glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4756 34# Issue is memory exhaustion via glob() calls, e.g. from within an ftp server 35# Best discussion in https://bugzilla.redhat.com/show_bug.cgi?id=681681 36# Upstream don't see it as a security issue, ftp servers shouldn't be passing 37# this to libc glob. Exclude as upstream have no plans to add BSD's GLOB_LIMIT or similar 38CVE_CHECK_IGNORE += "CVE-2010-4756" 39 40# go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29509 41# go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29511 42# The encoding/xml package in go can potentially be used for security exploits if not used correctly 43# CVE applies to a netapp product as well as flagging a general issue. We don't ship anything 44# exposing this interface in an exploitable way 45CVE_CHECK_IGNORE += "CVE-2020-29509 CVE-2020-29511" 46 47# db 48# Since Oracle relicensed bdb, the open source community is slowly but surely replacing bdb with 49# supported and open source friendly alternatives. As a result these CVEs are unlikely to ever be fixed. 50CVE_CHECK_IGNORE += "CVE-2015-2583 CVE-2015-2624 CVE-2015-2626 CVE-2015-2640 CVE-2015-2654 \ 51CVE-2015-2656 CVE-2015-4754 CVE-2015-4764 CVE-2015-4774 CVE-2015-4775 CVE-2015-4776 CVE-2015-4777 \ 52CVE-2015-4778 CVE-2015-4779 CVE-2015-4780 CVE-2015-4781 CVE-2015-4782 CVE-2015-4783 CVE-2015-4784 \ 53CVE-2015-4785 CVE-2015-4786 CVE-2015-4787 CVE-2015-4788 CVE-2015-4789 CVE-2015-4790 CVE-2016-0682 \ 54CVE-2016-0689 CVE-2016-0692 CVE-2016-0694 CVE-2016-3418 CVE-2020-2981" 55 56 57# 58# Kernel CVEs, e.g. linux-yocto* 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. 63# 64# Rather than just ignore all kernel CVEs, list the ones we ignore on this basis here, allowing new 65# issues to be visible. If anyone wishes to clean up CPE entries with NIST for these, we'd 66# welcome than and then entries can likely be removed from here. 67# 68# 1999-2010 69CVE_CHECK_IGNORE += "CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007-2764 CVE-2007-4998 CVE-2008-2544 \ 70 CVE-2008-4609 CVE-2010-0298 CVE-2010-4563" 71# 2011-2017 72CVE_CHECK_IGNORE += "CVE-2011-0640 CVE-2014-2648 CVE-2014-8171 CVE-2016-0774 CVE-2016-3695 CVE-2016-3699 \ 73 CVE-2017-1000255 CVE-2017-1000377 CVE-2017-5897 CVE-2017-6264" 74# 2018 75CVE_CHECK_IGNORE += "CVE-2018-1000026 CVE-2018-10840 CVE-2018-10876 CVE-2018-10882 CVE-2018-10901 CVE-2018-10902 \ 76 CVE-2018-14625 CVE-2018-16880 CVE-2018-16884 CVE-2018-5873 CVE-2018-6559" 77# 2019 78CVE_CHECK_IGNORE += "CVE-2019-10126 CVE-2019-14899 CVE-2019-18910 CVE-2019-3016 CVE-2019-3819 CVE-2019-3846 CVE-2019-3887" 79# 2020 80CVE_CHECK_IGNORE += "CVE-2020-10732 CVE-2020-10742 CVE-2020-16119 CVE-2020-1749 CVE-2020-25672 CVE-2020-27820 CVE-2020-35501 CVE-2020-8834" 81# 2021 82CVE_CHECK_IGNORE += "CVE-2021-20194 CVE-2021-20226 CVE-2021-20265 CVE-2021-3564 CVE-2021-3743 CVE-2021-3847 CVE-2021-4002 \ 83 CVE-2021-4090 CVE-2021-4095 CVE-2021-4197 CVE-2021-4202 CVE-2021-44879 CVE-2021-45402" 84# 2022 85CVE_CHECK_IGNORE += "CVE-2022-0185 CVE-2022-0264 CVE-2022-0286 CVE-2022-0330 CVE-2022-0382 CVE-2022-0433 CVE-2022-0435 \ 86 CVE-2022-0492 CVE-2022-0494 CVE-2022-0500 CVE-2022-0516 CVE-2022-0617 CVE-2022-0742 CVE-2022-0854 \ 87 CVE-2022-0995 CVE-2022-0998 CVE-2022-1011 CVE-2022-1015 CVE-2022-1048 CVE-2022-1055 CVE-2022-1195 \ 88 CVE-2022-1353 CVE-2022-24122 CVE-2022-24448 CVE-2022-24958 CVE-2022-24959 CVE-2022-25258 CVE-2022-25265 \ 89 CVE-2022-25375 CVE-2022-26490 CVE-2022-26878 CVE-2022-26966 CVE-2022-27223 CVE-2022-27666 CVE-2022-27950 \ 90 CVE-2022-28356 CVE-2022-28388 CVE-2022-28389 CVE-2022-28390 CVE-2022-28796 CVE-2022-28893 CVE-2022-29156 \ 91 CVE-2022-29582 CVE-2022-29968" 92 93 94# qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20255 95# There was a proposed patch https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06098.html 96# qemu maintainers say the patch is incorrect and should not be applied 97# Ignore from OE's perspectivee as the issue is of low impact, at worst sitting in an infinite loop rather than exploitable 98CVE_CHECK_IGNORE += "CVE-2021-20255" 99 100# qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-12067 101# There was a proposed patch but rejected by upstream qemu. It is unclear if the issue can 102# still be reproduced or where exactly any bug is. 103# Ignore from OE's perspective as we'll pick up any fix when upstream accepts one. 104CVE_CHECK_IGNORE += "CVE-2019-12067" 105 106# nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-18974 107# It is a fuzzing related buffer overflow. It is of low impact since most devices 108# wouldn't expose an assembler. The upstream is inactive and there is little to be 109# done about the bug, ignore from an OE perspective. 110CVE_CHECK_IGNORE += "CVE-2020-18974" 111 112 113 114