From: Brice Waegeneire <brice@waegenei.re>
To: 40142@debbugs.gnu.org
Subject: bug#40142: CVE checker return false positives
Date: Fri, 20 Mar 2020 09:10:31 +0000 [thread overview]
Message-ID: <0bb3b7878b37095b4ed7fa49aee5936f@waegenei.re> (raw)
Hello,
The CVE checker of “guix lint” returns false positives:
┌────
│ LANGUAGE=C guix lint git 2>&1
├───
│ gnu/packages/version-control.scm:149:2: git@2.25.1: probably
vulnerable to CVE-2020-2136, CVE-2019-1003010, CVE-2018-1000110,
CVE-2018-1000182
│
/gnu/store/8q0nfd6vnc6lnjh13rwl7fyimwlv7fml-guix-module-union/share/guile/site/3.0/gnu/packages/version-control.scm:153:12:
git@2.25.1: can be upgraded to 2.25.2
│
/gnu/store/8q0nfd6vnc6lnjh13rwl7fyimwlv7fml-guix-module-union/share/guile/site/3.0/gnu/packages/version-control.scm:154:11:
git@2.25.1: source not archived on Software Heritage
└────
• [CVE-2020-2136]: “Jenkins Git Plugin 4.2.0 and earlier […]”
• [CVE-2019-1003010]: “[…] Jenkins Git Plugin 3.9.1 and earlier […]”
• [CVE-2018-1000110]: “[…] Jenkins Git Plugin version 3.7.0 and earlier
[…]”
• [CVE-2018-1000182]: “[…] Jenkins Git Plugin 3.9.0 and older […]”
Also note the missing / on the first line and it output on `stderr'
instead of `stdout'.
[CVE-2020-2136] <https://nvd.nist.gov/vuln/detail/CVE-2020-2136>
[CVE-2019-1003010] <https://nvd.nist.gov/vuln/detail/CVE-2019-1003010>
[CVE-2018-1000110] <https://nvd.nist.gov/vuln/detail/CVE-2018-1000110>
[CVE-2018-1000182] <https://nvd.nist.gov/vuln/detail/CVE-2018-1000182>
Brice.
next reply other threads:[~2020-03-20 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 9:10 Brice Waegeneire [this message]
2020-03-21 16:25 ` bug#40142: CVE checker return false positives Ludovic Courtès
2020-03-21 16:57 ` Brice Waegeneire
2020-04-01 17:01 ` bug#40142: (guix cve) discards configuration "vendor", leading to " Brice Waegeneire
2020-04-02 10:38 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0bb3b7878b37095b4ed7fa49aee5936f@waegenei.re \
--to=brice@waegenei.re \
--cc=40142@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).