<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 01:42:55 +0000</lastBuildDate>
    <item>
      <title>certfr-2025-avi-0448 — De multiples vulnérabilités ont été découvertes dans Tenable Nessus Network Monitor. Certaines d'entre elles permettent…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0448</link>
      <description>certfr-2025-avi-0448</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0448</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-AS20822 — Security fix for CVE-2023-7256 applied in: calico-fips 3.31.2-r1</title>
      <link>https://127.0.0.1:10001/vuln/cleanstart-2026-as20822</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: calico-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the calico-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: calico-fips&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the calico-fips package. This issue is resolved in later releases. See references for vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cleanstart-2026-as20822</guid>
    </item>
    <item>
      <title>OESA-2024-2180 — libpcap security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: libpcap, openEuler:24.03-LTS: libpcap, openEuler:22.03-LTS-SP4: libpcap, openEuler:22.03-LTS-SP3: libpcap, openEuler:20.03-LTS-SP4: libpcap&lt;/p&gt;
&lt;p&gt;This is the official web site of tcpdump, a powerful command-line  packet analyzer; and libpcap, a portable C/C++ library for  network traffic capture.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns.  This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block.  A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.(CVE-2023-7256)&lt;/p&gt;
&lt;p&gt;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.(CVE-2024-8006)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: libpcap, openEuler:24.03-LTS: libpcap, openEuler:22.03-LTS-SP4: libpcap, openEuler:22.03-LTS-SP3: libpcap, openEuler:20.03-LTS-SP4: libpcap&lt;/p&gt;
&lt;p&gt;This is the official web site of tcpdump, a powerful command-line  packet analyzer; and libpcap, a portable C/C++ library for  network traffic capture.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns.  This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block.  A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.(CVE-2023-7256)&lt;/p&gt;
&lt;p&gt;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.(CVE-2024-8006)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2180</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2023-7256</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-7256</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libpcap, Ubuntu:Pro:16.04:LTS: libpcap, Ubuntu:Pro:18.04:LTS: libpcap, Ubuntu:20.04:LTS: libpcap, Ubuntu:22.04:LTS: libpcap, Ubuntu:24.04:LTS: libpcap&lt;/p&gt;
&lt;p&gt;In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns.  This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block.  A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libpcap, Ubuntu:Pro:16.04:LTS: libpcap, Ubuntu:Pro:18.04:LTS: libpcap, Ubuntu:20.04:LTS: libpcap, Ubuntu:22.04:LTS: libpcap, Ubuntu:24.04:LTS: libpcap&lt;/p&gt;
&lt;p&gt;In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns.  This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block.  A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2023-7256</guid>
    </item>
  </channel>
</rss>
