Microsoft security update for CVE-2024-8006
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-8006. This page also shows what EchelonGraph holds for CVE-2024-8006, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products8
- azl3 libpcap 1.10.4-1 on Azure Linux 3.0
- azl3 libpcap 1.10.5-1 on Azure Linux 3.0
- azl3 nmap 7.95-2 on Azure Linux 3.0
- cbl2 libpcap 1.10.1-3 on CBL Mariner 2.0
- cbl2 libpcap 1.10.1-4 on CBL Mariner 2.0
- cbl2 libpcap 1.10.1-4 on CBL-Mariner 2.0
- cbl2 nmap 7.93-3 on CBL Mariner 2.0
- cbl2 nmap 7.93-3 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 4 updates
4 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 1.10.1-3 |
| — | Security Update | 7.95-2 |
| — | Security Update | 1.10.5-1 |
| — | Security Update | 7.93-3 |
🧭 EchelonGraph on CVE-2024-8006
- EchelonGraph score
- 4.4 MEDIUM
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
Remote packet capture support is disabled by default in libpcap. When a user builds libpcap with remote packet capture support enabled, one of the functions that become available is pcap_findalldevs_ex(). One of the function arguments can be a filesystem path, which normally means a directory with input data files. When the specified path cannot be used as a directory, the function receives NULL from opendir(), but does not check the return value and passes the NULL value to readdir(), which causes a NULL pointer derefence.
Published by Tcpdump Group, the CVE Numbering Authority that assigned CVE-2024-8006, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).