Skip to contentSkip to conversation

OE-core CVE metrics for master on Sun 03 Mar 2024 01:00:01 AM HST

DISCUSSION [email protected] 7 participants 9 messages Mar 3, 2024 – Mar 5, 2024

lore
Share & tools
lore
#0 lore raw

Branch: master

New this week: 2 CVEs
CVE-2024-25739 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25739 * CVE-2024-25740 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25740 *

Removed this week: 3 CVEs
CVE-2024-23850 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23850 * CVE-2024-23851 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23851 * CVE-2024-24860 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24860 *

Full list: Found 41 unpatched CVEs
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 * CVE-2021-3714 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 * CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 * CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 * CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 * CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 * CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 * CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 * CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 * CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 * CVE-2023-3397 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3397 * CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 * CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 * CVE-2023-42363 (CVSS3: 5.5 MEDIUM): busybox https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42363 * CVE-2023-42364 (CVSS3: 5.5 MEDIUM): busybox https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42364 * CVE-2023-42365 (CVSS3: 5.5 MEDIUM): busybox https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42365 * CVE-2023-42366 (CVSS3: 5.5 MEDIUM): busybox https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42366 * CVE-2023-51767 (CVSS3: 7.0 HIGH): openssh https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51767 * CVE-2023-6238 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6238 * CVE-2023-6240 (CVSS3: 6.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6240 * CVE-2023-6270 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6270 * CVE-2023-6356 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6356 * CVE-2023-6535 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6535 * CVE-2023-6536 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6536 * CVE-2023-6683 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6683 * CVE-2023-6780 (CVSS3: 5.3 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6780 * CVE-2023-7042 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-7042 * CVE-2023-7216 (CVSS3: 8.8 HIGH): cpio https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-7216 * CVE-2024-0684 (CVSS3: 5.5 MEDIUM): coreutils:coreutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-0684 * CVE-2024-0841 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-0841 * CVE-2024-21803 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-21803 * CVE-2024-23307 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23307 * CVE-2024-23848 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23848 * CVE-2024-24857 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24857 * CVE-2024-24858 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24858 * CVE-2024-24859 (CVSS3: 4.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24859 * CVE-2024-24861 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24861 * CVE-2024-24864 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24864 * CVE-2024-25062 (CVSS3: 7.5 HIGH): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25062 * CVE-2024-25739 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25739 * CVE-2024-25740 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25740 *

Summary of CVE counts by recipe:
linux-yocto: 28
busybox: 4
qemu:qemu-native:qemu-system-native: 2
coreutils:coreutils-native: 1
cpio: 1
glibc: 1
gnupg:gnupg-native: 1
libxml2:libxml2-native: 1
nasm:nasm-native: 1
openssh: 1

For further information see: https://autobuilder.yocto.io/pub/non-release/patchmetrics/

#1 lore raw

Hi all,

quick check: No news for any old issue, except cpio, which is disputed by the maintainer.

Simone

Quoted 3 lines

Branch: master

New this week: 2 CVEs

...

Quoted 1 line

Removed this week: 3 CVEs

wiki updated

Quoted 5 lines

Full list:  Found 41 unpatched CVEs
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *
CVE-2021-3714 (CVSS3: 5.9 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *

Quoted 8 lines

CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *

Patch available but not reviewed upstream

Quoted 6 lines

CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *

upstream still open

Quoted 2 lines

CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *

upstream still open

Quoted 6 lines

CVE-2023-3397 (CVSS3: 6.3 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3397 *
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *

Quoted 8 lines

CVE-2023-42363 (CVSS3: 5.5 MEDIUM): busybox
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42363 *
CVE-2023-42364 (CVSS3: 5.5 MEDIUM): busybox
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42364 *
CVE-2023-42365 (CVSS3: 5.5 MEDIUM): busybox
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42365 *
CVE-2023-42366 (CVSS3: 5.5 MEDIUM): busybox
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42366 *

busybox: all still open upstream

Quoted 7 lines

CVE-2023-51767 (CVSS3: 7.0 HIGH): openssh
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51767 *
CVE-2023-6238 (CVSS3: 6.7 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6238 *
CVE-2023-6240 (CVSS3: 6.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6240 *
CVE-2023-6270 (CVSS3: 7.0 HIGH): linux-yocto

Quoted 8 lines

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6270 *
CVE-2023-6356 (CVSS3: 7.5 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6356 *
CVE-2023-6535 (CVSS3: 7.5 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6535 *
CVE-2023-6536 (CVSS3: 7.5 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6536 *
CVE-2023-6683 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native

patch in master-next

Quoted 3 lines

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6683 *
CVE-2023-6780 (CVSS3: 5.3 MEDIUM): glibc
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6780 *

Should be gone soon, got mail from NVD that it will be updated

Quoted 4 lines

CVE-2023-7042 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-7042 *
CVE-2023-7216 (CVSS3: 8.8 HIGH): cpio
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-7216 *

Disputed by upstream maintainer as intended. I would set a CVE_STATUS soon.

Quoted 2 lines

CVE-2024-0684 (CVSS3: 5.5 MEDIUM): coreutils:coreutils-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-0684 *

patch in master-next

Quoted 12 lines

CVE-2024-0841 (CVSS3: 7.8 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-0841 *
CVE-2024-21803 (CVSS3: 7.8 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-21803 *
CVE-2024-23307 (CVSS3: 7.8 HIGH): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23307 *
CVE-2024-23848 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23848 *
CVE-2024-24857 (CVSS3: 6.8 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24857 *
CVE-2024-24858 (CVSS3: 5.3 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24858 *

Quoted 8 lines

CVE-2024-24859 (CVSS3: 4.8 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24859 *
CVE-2024-24861 (CVSS3: 6.3 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24861 *
CVE-2024-24864 (CVSS3: 4.7 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24864 *
CVE-2024-25062 (CVSS3: 7.5 HIGH): libxml2:libxml2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25062 *

If libxml2 gets updated webkitgtk build fails still

Quoted 31 lines

CVE-2024-25739 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25739 *
CVE-2024-25740 (CVSS3: 5.5 MEDIUM): linux-yocto
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25740 *

Summary of CVE counts by recipe:
  linux-yocto: 28
  busybox: 4
  qemu:qemu-native:qemu-system-native: 2
  coreutils:coreutils-native: 1
  cpio: 1
  glibc: 1
  gnupg:gnupg-native: 1
  libxml2:libxml2-native: 1
  nasm:nasm-native: 1
  openssh: 1

For further information see:
https://autobuilder.yocto.io/pub/non-release/patchmetrics/

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#1086):
https://lists.yoctoproject.org/g/yocto-security/message/1086
Mute This Topic: https://lists.yoctoproject.org/mt/104700791/8052774
Group Owner: [email protected] Unsubscribe:
https://lists.yoctoproject.org/g/yocto-security/unsub [[email protected]
]
-=-=-=-=-=-=-=-=-=-=-=-

#3 lore raw
Quoted 7 lines · Richard Purdie
Quoted 1 line · Simone Weiß
Quoted 1 line

Full list: Found 41 unpatched CVEs

I'm a bit puzzled/worried that our patch metrics page says 50 rather than 41:

Quoted 6 lines

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt

:/

Does anyone know why?

Weird...

Here is the added CVEs from Steve's run to the AB run (
https://autobuilder.yoctoproject.org/typhoon/#/builders/138/builds/1275/steps/15/logs/stdio
):
+CVE-2022-3563: bluez5
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 * +CVE-2022-3637: bluez5
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3637 * +CVE-2023-28736: mdadm
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28736 * +CVE-2023-28938: mdadm
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 * +CVE-2023-3180: qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 * +CVE-2023-3354: qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 * +CVE-2023-4135: qemu:qemu-native:qemu-system-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 * +CVE-2023-6918: libssh2:libssh2-native
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6918 * +CVE-2024-24806: libuv
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24806 *

I've started looking at this at the top:
CVE-2022-3563: bluez5
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 * => Fixed in >= 5.65 (last NVD update November 2023), bluez5 is 5.72 in oe-core but cve-check says Unpatched :
https://git.yoctoproject.org/yocto-metrics/tree/cve-check/master/1709449295.json?id=851f9dd3bf9faccb85796b45e62139cc50cbbcb7#n12305
Locally this CVE is not displayed as unpatched.

The rest of the list is in similar state:
* oe-core is updated enough for the CVE to be patched as per NVD data
* all NVD updates are at least a few weeks old (except CVE-2024-24806:
libuv : 4 days)
* locally these CVE do not appear as Unpatched

Something is weird on the autobuilder. Maybe keep the build directory around and a copy of the current CVE database for analysis ($DL_DIR/CVE_CHECK/nvdcve_2-1.db) ?

Quoted 15 lines

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#1089):
https://lists.yoctoproject.org/g/yocto-security/message/1089
Mute This Topic: https://lists.yoctoproject.org/mt/104700791/4316185
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto-security/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 2 lines
Yoann Congal
Smile ECS - Tech expert
#4 lore raw
In reply to Richard Purdie

I already mentioned this last week.
https://lists.openembedded.org/g/openembedded-core/message/196199

I think that partial NVD DB update is not working properly as things which were corrected by NVD are still showing up in patchmetrics but not in email reports.

For example:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6779
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6780
kirkstone has glibc 2.35 and nvd recently fixed these to >= 2.37 and these ate still in patchmetrics.

Email reports maybe use different (not-broken yet) NVD DB cache or make full update instead of incremental?

Peter

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Richard Purdie via lists.yoctoproject.org
Sent: Sunday, March 3, 2024 13:36
To: Simone Weiß <[email protected]>; Steve Sakoman <[email protected]>; [email protected]; [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for master on Sun 03 Mar 2024 01:00:01 AM HST

Quoted 20 lines · Simone Weiß
Quoted 2 lines

quick check: No news for any old issue, except cpio, which is disputed by the maintainer.

Thanks, that is really useful to know!

Quoted 2 lines
Quoted 2 lines

Full list:  Found 41 unpatched CVEs

I'm a bit puzzled/worried that our patch metrics page says 50 rather than 41:

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt

:/

Does anyone know why?

Cheers,

Richard

#5 lore raw
Quoted 7 lines · Peter Marko via lists.yoctoproject.org

I already mentioned this last week.
https://lists.openembedded.org/g/openembedded-core/message/196199

I think that partial NVD DB update is not working properly as things which were corrected by NVD are still showing up in patchmetrics but not in email reports.

The yocto-metrics repo shows that CVE-2022-3563 has been "Unpatched" since its creation 31/10/2023.
+1 on the "partial NVD DB update is not working properly" hyptohesis

Looking into this, I've started to look at the NVD API: IIUC, a partial update is done by requesting every CVE that have a lastModified field after our last update.

But from the NVD API doc:
https://nvd.nist.gov/developers/vulnerabilities#cves-lastModDates

Quoted 4 lines

A CVE's lastModified *does* *not* change when any of the follow actions occur:
[...]
The NVD modifies a CPE record previously associated with the CVE record

If I read that correctly, this means that CVEs CPE updated by the NVD (which is what we frequently request to the NVD) would not have their lastModified
field updated and then, missed by the partial update. Sounds like a bug, no?

For example:

Quoted 55 lines

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6779
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6780
kirkstone has glibc 2.35 and nvd recently fixed these to >= 2.37 and these ate still in patchmetrics.

Email reports maybe use different (not-broken yet) NVD DB cache or make full update instead of incremental?

Peter

-----Original Message-----
From: [email protected] < [email protected]> On Behalf Of Richard Purdie via lists.yoctoproject.org
Sent: Sunday, March 3, 2024 13:36
To: Simone Weiß <[email protected]>; Steve Sakoman < [email protected]>; [email protected]; [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for master on Sun 03 Mar 2024 01:00:01 AM HST

Quoted 10 lines · Simone Weiß
Quoted 2 lines

quick check: No news for any old issue, except cpio, which is disputed by the maintainer.

Thanks, that is really useful to know!

Quoted 2 lines
Quoted 2 lines

Full list: Found 41 unpatched CVEs

I'm a bit puzzled/worried that our patch metrics page says 50 rather

than 41:

Quoted 2 lines

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt

Quoted 8 lines

:/

Does anyone know why?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#1091):
https://lists.yoctoproject.org/g/yocto-security/message/1091
Mute This Topic: https://lists.yoctoproject.org/mt/104700791/4316185
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto-security/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 2 lines
Yoann Congal
Smile ECS - Tech expert
#6 lore raw
Quoted 30 lines · Yoann CONGAL
Quoted 7 lines · Peter Marko via lists.yoctoproject.org

I already mentioned this last week.
https://lists.openembedded.org/g/openembedded-core/message/196199

I think that partial NVD DB update is not working properly as things which were corrected by NVD are still showing up in patchmetrics but not in email reports.

The yocto-metrics repo shows that CVE-2022-3563 has been "Unpatched" since its creation 31/10/2023.
+1 on the "partial NVD DB update is not working properly" hyptohesis

Looking into this, I've started to look at the NVD API: IIUC, a partial update is done by requesting every CVE that have a lastModified field after our last update.

But from the NVD API doc:
https://nvd.nist.gov/developers/vulnerabilities#cves-lastModDates

Quoted 4 lines

A CVE's lastModified *does* *not* change when any of the follow actions occur:
[...]
The NVD modifies a CPE record previously associated with the CVE record

Quoted 4 lines

If I read that correctly, this means that CVEs CPE updated by the NVD (which is what we frequently request to the NVD) would not have their lastModified field updated and then, missed by the partial update. Sounds like a bug, no?

Hmmm, maybe not so simple: Take CVE-2023-3180 for exemple:
* https://nvd.nist.gov/vuln/detail/CVE-2023-3180#VulnChangeHistorySection
=> last update (2023-11-07) is the CPE update adding an upper bound to the version
* but CVE lastmodified field does match the CPE update date (2023-11-07) :
https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2023-3180

At least, right now, the API output is "correct" (but does not match my understanding of the doc). But, maybe it was "incorrect" (but matching the doc) a few months ago?

Quoted 62 lines

For example:

Quoted 45 lines

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6779
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6780
kirkstone has glibc 2.35 and nvd recently fixed these to >= 2.37 and these ate still in patchmetrics.

Email reports maybe use different (not-broken yet) NVD DB cache or make full update instead of incremental?

Peter

-----Original Message-----
From: [email protected] < [email protected]> On Behalf Of Richard Purdie via lists.yoctoproject.org
Sent: Sunday, March 3, 2024 13:36
To: Simone Weiß <[email protected]>; Steve Sakoman < [email protected]>; [email protected]; [email protected]
Subject: Re: [yocto-security] OE-core CVE metrics for master on Sun 03 Mar 2024 01:00:01 AM HST

Quoted 2 lines · Simone Weiß
Quoted 1 line

quick check: No news for any old issue, except cpio, which is

disputed

Quoted 8 lines
Quoted 1 line

by the maintainer.

Thanks, that is really useful to know!

Quoted 2 lines
Quoted 2 lines

Full list: Found 41 unpatched CVEs

I'm a bit puzzled/worried that our patch metrics page says 50 rather

than 41:

Quoted 2 lines

https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt

Quoted 8 lines

:/

Does anyone know why?

Cheers,

Richard

Quoted 11 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#1091):
https://lists.yoctoproject.org/g/yocto-security/message/1091
Mute This Topic: https://lists.yoctoproject.org/mt/104700791/4316185
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto-security/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

--
Yoann Congal
Smile ECS - Tech expert

Signature · 2 lines
Yoann Congal
Smile ECS - Tech expert
#7 lore raw
In reply to Marko, Peter
Quoted 5 lines · Peter Marko via lists.yoctoproject.org

I already mentioned this last week.
https://lists.openembedded.org/g/openembedded-core/message/196199

I think that partial NVD DB update is not working properly as things which were corrected by NVD are still showing up in patchmetrics but not in email reports.

I need to file a bug for this issue. If CPEs are updated then they only reach an existing database if the CVE itself is updated, as a CPE change alone isn’t enough to appear in the query we use.

I’ve a branch that adds this second query to the fetcher but it is incredibly slow (and you thought the current fetcher was slow?) and still isn’t 100% accurate. NIST are aware of “limitations” with the new API…

For accurate runs I do sadly recommend forcing a full fetch of the CVE data.

Ross

#8 lore raw
Quoted 6 lines · Ross Burton
Quoted 4 lines · Peter Marko via lists.yoctoproject.org

I already mentioned this last week.
https://lists.openembedded.org/g/openembedded-core/message/196199

Quoted 8 lines
Quoted 1 line

I think that partial NVD DB update is not working properly as things which were corrected by NVD are still showing up in patchmetrics but not in email reports.

I need to file a bug for this issue. If CPEs are updated then they only reach an existing database if the CVE itself is updated, as a CPE change alone isn’t enough to appear in the query we use.

I’ve a branch that adds this second query to the fetcher but it is incredibly slow (and you thought the current fetcher was slow?) and still isn’t 100% accurate. NIST are aware of “limitations” with the new API…

For accurate runs I do sadly recommend forcing a full fetch of the CVE data.

I second Ross that we're likely hitting that problem. We have discussed that with Ross before and there seems to be no workaround other than to download the whole database.

Solutions I see:
- always fetch the whole database
- go back to the old legacy system with JSON dumps (which is still online)
- have an "official" YP mirror of the database

Probably a subject we could discuss at the today's call.

Kind regards,
Marta