<?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://cve.radiocsirt.org</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, 10 Oct 2026 21:44:51 +0000</lastBuildDate>
    <item>
      <title>certa-2013-avi-206 — De multiples vulnérabilités ont été corrigées dans les produits &lt;span
class="textit"&gt;Asterisk&lt;/span&gt;. Elles permettent…</title>
      <link>https://cve.radiocsirt.org/vuln/certa-2013-avi-206</link>
      <description>certa-2013-avi-206</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certa-2013-avi-206</guid>
    </item>
    <item>
      <title>EUVD-2026-166301</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-166301</link>
      <description>EUVD-2026-166301</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-166301</guid>
    </item>
    <item>
      <title>fkie_cve-2013-2264</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2013-2264</link>
      <description>&lt;p&gt;The SIP channel driver in Asterisk Open Source 1.8.x before 1.8.20.2, 10.x before 10.12.2, and 11.x before 11.2.2; Certified Asterisk 1.8.15 before 1.8.15-cert2; Asterisk Business Edition (BE) C.3.x before C.3.8.1; and Asterisk Digiumphones 10.x-digiumphones before 10.12.2-digiumphones exhibits different behavior for invalid INVITE, SUBSCRIBE, and REGISTER transactions depending on whether the user account exists, which allows remote attackers to enumerate account names by (1) reading HTTP status codes, (2) reading additional text in a 403 (aka Forbidden) response, or (3) observing whether certain retransmissions occur.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SIP channel driver in Asterisk Open Source 1.8.x before 1.8.20.2, 10.x before 10.12.2, and 11.x before 11.2.2; Certified Asterisk 1.8.15 before 1.8.15-cert2; Asterisk Business Edition (BE) C.3.x before C.3.8.1; and Asterisk Digiumphones 10.x-digiumphones before 10.12.2-digiumphones exhibits different behavior for invalid INVITE, SUBSCRIBE, and REGISTER transactions depending on whether the user account exists, which allows remote attackers to enumerate account names by (1) reading HTTP status codes, (2) reading additional text in a 403 (aka Forbidden) response, or (3) observing whether certain retransmissions occur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2013-2264</guid>
    </item>
    <item>
      <title>GHSA-79cp-774x-5w3c</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-79cp-774x-5w3c</link>
      <description>&lt;p&gt;The SIP channel driver in Asterisk Open Source 1.8.x before 1.8.20.2, 10.x before 10.12.2, and 11.x before 11.2.2; Certified Asterisk 1.8.15 before 1.8.15-cert2; Asterisk Business Edition (BE) C.3.x before C.3.8.1; and Asterisk Digiumphones 10.x-digiumphones before 10.12.2-digiumphones exhibits different behavior for invalid INVITE, SUBSCRIBE, and REGISTER transactions depending on whether the user account exists, which allows remote attackers to enumerate account names by (1) reading HTTP status codes, (2) reading additional text in a 403 (aka Forbidden) response, or (3) observing whether certain retransmissions occur.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SIP channel driver in Asterisk Open Source 1.8.x before 1.8.20.2, 10.x before 10.12.2, and 11.x before 11.2.2; Certified Asterisk 1.8.15 before 1.8.15-cert2; Asterisk Business Edition (BE) C.3.x before C.3.8.1; and Asterisk Digiumphones 10.x-digiumphones before 10.12.2-digiumphones exhibits different behavior for invalid INVITE, SUBSCRIBE, and REGISTER transactions depending on whether the user account exists, which allows remote attackers to enumerate account names by (1) reading HTTP status codes, (2) reading additional text in a 403 (aka Forbidden) response, or (3) observing whether certain retransmissions occur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-79cp-774x-5w3c</guid>
    </item>
    <item>
      <title>gsd-2013-2264</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2013-2264</link>
      <description>gsd-2013-2264</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2013-2264</guid>
    </item>
  </channel>
</rss>
