Re: [oniro-dev] CVE status for 2.0

[Davide Ricci <davide.ricci@xxxxxxxxxx>]

Stupid me,

 

An excel sheet was attached … I am reviewing it now.

 

D

 

From: oniro-dev <oniro-dev-bounces@xxxxxxxxxxx> On Behalf Of Davide Ricci
Sent: giovedì 24 novembre 2022 15:12
To: Marta Rybczynska <marta.rybczynska@xxxxxxxxxx>; onirocore developer discussions <oniro-dev@xxxxxxxxxxx>
Subject: Re: [oniro-dev] CVE status for 2.0

 

Since we are aware of the issues, we ought to try to fix the most sever ones – do we have the breakdown and know how many CVEs per CVSS severity class do we have?

 

Thanks

D

 

From: Marta Rybczynska <marta.rybczynska@xxxxxxxxxx>
Sent: giovedì 24 novembre 2022 14:30
To: Davide Ricci <davide.ricci@xxxxxxxxxx>; onirocore developer discussions <oniro-dev@xxxxxxxxxxx>
Subject: CVE status for 2.0

 

Dear all,

I have first results of CVE checks for the upcoming 2.0. For simplification, you have the details from the qemu x86-64 image (rootfs only, excluding SDK).

 

With the database of yesterday, we have 378 issues. Out of that:

4 at or above CVSSv3 9.0 (curl, libpam, 2xlinux)

122 at or above CVSSv3 7.5 (including the openssl issue that made the news, expat, python, dropbear)

 

Apart from the Linux kernel, most should go away with a kirkstone update.

 

The question is if we release like that or we spend time to fix issues above certain CVSS (like 9.0 or 8.0)?

 

Kind regards,

Marta