cve-extra-exclusions.inc: add exclusion list for intractable CVE's
PATCH 1/1 cve-extra-exclusions.inc: add exclusion list for intractable CVE's
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environment
In some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
--- .../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 meta/conf/distro/include/cve-extra-exclusions.inc
meta/conf/distro/include/cve-extra-exclusions.inc new file +18 -0
@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about +# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006" + +# groff:groff-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0803 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0803" +
Signature · 1 line
2.25.1
Hi,
Quoted 29 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentIn some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>--- .../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 meta/conf/distro/include/cve-extra-exclusions.incmeta/conf/distro/include/cve-extra-exclusions.inc new file +2
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about
meta/conf/distro/include/cve-extra-exclusions.inc line 12
Quoted 10 lines
meta/conf/distro/include/cve-extra-exclusions.inc new file +10
-0+# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006"
Could this be specific to a recipe?
It may be that CVE data changes and adds new CPEs and the same CVE could still be valid for another recipe. I think the analysis also applies to a single recipe.
Cheers,
-Mikko
Quoted 45 lines · Mikko Rapeli
Hi,
Quoted 29 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentIn some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>---
.../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++1 file changed, 18 insertions(+)create mode 100644 meta/conf/distro/include/cve-extra-exclusions.inc
meta/conf/distro/include/cve-extra-exclusions.inc new file +2
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis aboutmeta/conf/distro/include/cve-extra-exclusions.inc line 12
Quoted 10 lines
meta/conf/distro/include/cve-extra-exclusions.inc new file +10
-0+# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006"Could this be specific to a recipe?
Quoted 3 lines
It may be that CVE data changes and adds new CPEs and the same CVE could still be valid for another recipe. I think the analysis also applies to a single recipe.
I've been discussing this with Steve a bit. My concern and motivation for this is that we have a set of CVEs which are proving hard to find any useful data about and that we can do little to address, particularly the ones 10-20 years old. Having those showing up on weekly reports when we can do little about them is painting the situation a little unfairly. Whitelisting them in the recipes is also not entirely appropriate though. This file is primarily intended to collect up a list of those along with what information we do know.
For more recent entries with better data, I'd expect we either fix them or we can handle on a per recipe basis. The entries in this file are likely to be the really old ones which are very unlikely to change.
We've left the file as opt-in so users have to choose whether they want this data but it gives us a way to document any investigation done and what the status is.
In answer to the specific question, we could likely use pn- overrides here I guess but for the kinds of CVEs likely to be listed, I'm not sure it gains us much?
Cheers,
Richard
Quoted 45 lines · Mikko Rapeli
Hi,
Quoted 29 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentIn some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>--- .../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)create mode 100644 meta/conf/distro/include/cve-extra-exclusions.inc
meta/conf/distro/include/cve-extra-exclusions.inc new file +2
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis aboutmeta/conf/distro/include/cve-extra-exclusions.inc line 12
Quoted 10 lines
meta/conf/distro/include/cve-extra-exclusions.inc new file +10
-0+# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006"Could this be specific to a recipe?
Quoted 3 lines
It may be that CVE data changes and adds new CPEs and the same CVE could still be valid for another recipe. I think the analysis also applies to a single recipe.
My understanding of this file is, that it targets CVEs that will never be fixed - so it just reduces the noise from a scan - the same settings can still be applied to any kind of recipe.
But what I'd like to see is a proper documentation of this inc file so it gets some visibility - or alternatively it's included by default.
or it might be even okay to include these settings into the cvecheck.bbclass as an opt-out feature - simply any place but an undocumented inc-file
Quoted 9 lines
Cheers,
-Mikko
Quoted 7 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environment
I do see the desire of doing this as it is one file to maintain if there are multiple packages being updated at once. This does highlight a few things to me:
1) We have been dealing with this on a per-recipe basis. This is a shift from that. ( Does this need to be documented)
2) Recipe Maintainers aren't engage in this area of activity as we had original hoped. So we are working around that.
Reporting a false positive is better than masking an actual issue IMHO. So what was the Policy used to decide on what can be put into this file? Did I miss that conversion ? Is it documented anywhere?
- Armin
Quoted 40 lines
In some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>--- .../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 meta/conf/distro/include/cve-extra-exclusions.incmeta/conf/distro/include/cve-extra-exclusions.inc new file +18
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about +# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006" + +# groff:groff-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0803 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0803" +
Quoted 11 lines · On Sun, May 9, 2021 at 8:17 AM akuster808 <[email protected]> wrote:
Quoted 7 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentI do see the desire of doing this as it is one file to maintain if there are multiple packages being updated at once.
No, that isn't the intent of this at all! The above four methods are still the desired method to deal with CVE's on a per recipe basis, even if a CVE applies to multiple packages (quite rare).
Quoted 5 lines
This does highlight a few
things to me:1) We have been dealing with this on a per-recipe basis. This is a shift from that. ( Does this need to be documented)
As I stated above, this is not the intent.
Quoted 2 lines
2) Recipe Maintainers aren't engage in this area of activity as we had original hoped. So we are working around that.
True, they haven't. But, no, working around lack of engagement is not the intent! See my last two paragraphs in the original patch for my intent.
Quoted 1 line
Reporting a false positive is better than masking an actual issue IMHO.
I agree completely, and this is why this mechanism is optional.
Quoted 2 lines
So what was the Policy used to decide on what can be put into this file? Did I miss that conversion ? Is it documented anywhere?
See the next two paragraphs from the original patch. If you have some suggestions on how to better explain that this file is for ancient/intractable CVE's I would be happy to update the wording so there is no confusion!
Same goes for the leading comment in the include file. Suggestions for revisions to the wording are welcome!
Quoted 42 lines
Quoted 40 lines
In some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>--- .../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 meta/conf/distro/include/cve-extra-exclusions.incmeta/conf/distro/include/cve-extra-exclusions.inc new file +18
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about +# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results + +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006" + +# groff:groff-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0803 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0803" +
Quoted 13 lines · Armin Kuster
Quoted 7 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentI do see the desire of doing this as it is one file to maintain if there are multiple packages being updated at once. This does highlight a few things to me:
Quoted 6 lines
1) We have been dealing with this on a per-recipe basis. This is a shift from that. ( Does this need to be documented)
2) Recipe Maintainers aren't engage in this area of activity as we had original hoped. So we are working around that.
Reporting a false positive is better than masking an actual issue IMHO.
Steve has covered most things in his reply but I want to add something on this last bit.
Right now, multiple people have gone off and looked at some of these CVEs and all the people I know who have done it concluded they're intractable, there is nothing we can do about them.
I'd like to document this somewhere to save people doing the same work over and over. If someone wants to investigate further and can propose actual fixes, great, but it is helpful for them to have what we know so far to start from.
This patch is effectively there to start a discussion if necessary. I do strongly believe we need to do something here though as the false positives *are* harmful. Currently, it looks like the project doesn't care about 60 odd CVEs in master. Anyone wanting to try and improve that has to guess which ones have been investigated and which haven't.
Cheers,
Richard
Quoted 34 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentIn some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>---
.../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++1 file changed, 18 insertions(+)create mode 100644 meta/conf/distro/include/cve-extra-exclusions.inc
meta/conf/distro/include/cve-extra-exclusions.inc new file +7
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about +# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results
meta/conf/distro/include/cve-extra-exclusions.inc line 17
Quoted 10 lines
meta/conf/distro/include/cve-extra-exclusions.inc new file +10
-0+ +# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006" + +# groff:groff-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0803 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0803"
I was thinking of adding a better description for this one and went digging. I then found (I think?) that the above was fixed in:
https://git.savannah.gnu.org/cgit/groff.git/commit/?id=07f95f1674217275ed4612f1dcaa95a88435c6a7
which would make it fixed in groff 1.17. We can probably submit a request to update the CPE on that one...
I do think we're going to need this file and that having it might encourage people to either document issues or as I maybe found here, get to the bottom of one..
Cheers,
Richard
Quoted 35 lines · Steve Sakoman
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE does not apply to our environmentIn some cases none of these methods are possible. For example the CVE may be decades old with no apparent resolution, and with broken links that make further research impractical.
This patch creates a mechanism for users to remove this type of CVE from the cve-check results via an optional include file.
Signed-off-by Steve Sakoman <[email protected]>---
.../distro/include/cve-extra-exclusions.inc | 18 ++++++++++++++++++1 file changed, 18 insertions(+)create mode 100644 meta/conf/distro/include/cve-extra-exclusions.inc
meta/conf/distro/include/cve-extra-exclusions.inc new file +8
-0@@ -0,0 +1,18 @@ +# This file contains a list of CVE's where resolution has proven to be impractical. +# It contains all the information we are aware of about an issue and analysis about +# why we believe it can't be fixed/handled. Additional information is welcome through +# patches to the file. +# +# Include this file in your local.conf or distro.conf to exclude these CVE's +# from the cve-check results +
meta/conf/distro/include/cve-extra-exclusions.inc line 18
Quoted 10 lines
meta/conf/distro/include/cve-extra-exclusions.inc new file +10
-0+# strace https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0006 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0006" + +# groff:groff-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2000-0803 +# CVE is more than 20 years old with no resolution evident +# broken links in CVE database references make resolution impractical +CVE_CHECK_WHITELIST += "CVE-2000-0803" +
One I propose we could add which I'd looked into previously:
# epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-0238 # The issue here is spoofing of domain names using characters from other character sets. # There has been much discussion amongst the epiphany and webkit developers and # whilst there are improvements about how domains are handled and displayed to the user # there is unlikely ever to be a single fix to webkit or epiphany which addresses this # problem. Whitelisted as there isn't any mitigation or fix or way to progress this further # we can seem to take. CVE_CHECK_WHITELIST += "CVE-2005-0238"
Cheers,
Richard