Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "akuster" <akuster808@gmail.com>
To: Konrad Weihmann <kweihmann@outlook.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] cve-check breaks on zeus
Date: Sat, 25 Jul 2020 07:52:19 -0700	[thread overview]
Message-ID: <f1b775ff-0fbb-2444-ec91-5efea2f75868@gmail.com> (raw)
In-Reply-To: <AM7PR05MB6881998FE5ADEC576D81902CA8740@AM7PR05MB6881.eurprd05.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2077 bytes --]



On 7/25/20 4:13 AM, Konrad Weihmann wrote:
> Hi all,
>
> I'm just too lazy to check if that has been fixed in master already,
> but since yesterday cve-check breaks on zeus for me with the following

I think I just saw this on master. We need to check if NVD changed their
format again.

-armin

>
> File:
> '/opt/build/poky/meta/recipes-core/meta/cve-update-db-native.bb',
> lineno: 91, function: do_populate_cve_db
>      0087:            # Update db with current year json file
>      0088:            try:
>      0089:                response = urllib.request.urlopen(json_url)
>      0090:                if response:
>  *** 0091:                    update_db(c,
> gzip.decompress(response.read()).decode('utf-8'))
>      0092:                c.execute("insert or replace into META
> values (?, ?)", [year, last_modified])
>      0093:            except urllib.error.URLError as e:
>      0094:                cve_f.write('Warning: CVE db update error,
> CVE data is outdated.\n\n')
>      0095:                bb.warn("Cannot parse CVE data (%s), update
> failed" % e.reason)
> File:
> '/opt/build/poky/meta/recipes-core/meta/cve-update-db-native.bb',
> lineno: 173, function: update_db
>      0169:
>      0170:        cveId = elt['cve']['CVE_data_meta']['ID']
>      0171:        cveDesc =
> elt['cve']['description']['description_data'][0]['value']
>      0172:        date = elt['lastModifiedDate']
>  *** 0173:        accessVector =
> elt['impact']['baseMetricV2']['cvssV2']['accessVector']
>      0174:        cvssv2 =
> elt['impact']['baseMetricV2']['cvssV2']['baseScore']
>      0175:
>      0176:        try:
>      0177:            cvssv3 =
> elt['impact']['baseMetricV3']['cvssV3']['baseScore']
> Exception: KeyError: 'baseMetricV2'
>
> Cheers
> Konrad
>
> 


[-- Attachment #2: Type: text/html, Size: 3211 bytes --]

  reply	other threads:[~2020-07-25 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-25 11:13 cve-check breaks on zeus Konrad Weihmann
2020-07-25 14:52 ` akuster [this message]
2020-07-26  9:15   ` [OE-core] " Konrad Weihmann

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1b775ff-0fbb-2444-ec91-5efea2f75868@gmail.com \
    --to=akuster808@gmail.com \
    --cc=kweihmann@outlook.com \
    --cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox