<?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://db.gcve.eu</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>Mon, 28 Sep 2026 13:38:32 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-45084</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-45084</link>
      <description>&lt;p&gt;OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module&amp;#39;s handle_publish() function processes a SIP PUBLISH request with an Event: presence header and a message body while the configuration option enable_sphere_check=1 is set, it invokes the get_content_type() macro without first calling parse_content_type_hdr(), causing it to dereference uninitialized or NULL Content-Type parsing state and crash. If a Content-Type header is present but unparsed, msg-&amp;gt;content_type-&amp;gt;parsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg-&amp;gt;content_type itself is NULL, and both cases lead to a crash. A remote attacker can therefore cause a denial of service against an affected instance with a single PUBLISH request over UDP or TCP, using either a valid Content-Type: application/pidf+xml request or one with the header removed, and the vulnerable code path itself does not enforce authentication (though a deployment&amp;#39;s routing configuration may require it before this route is reached). The issue has been fixed in version 3.6.6 and 4.0.0-rc1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module&amp;#39;s handle_publish() function processes a SIP PUBLISH request with an Event: presence header and a message body while the configuration option enable_sphere_check=1 is set, it invokes the get_content_type() macro without first calling parse_content_type_hdr(), causing it to dereference uninitialized or NULL Content-Type parsing state and crash. If a Content-Type header is present but unparsed, msg-&amp;gt;content_type-&amp;gt;parsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg-&amp;gt;content_type itself is NULL, and both cases lead to a crash. A remote attacker can therefore cause a denial of service against an affected instance with a single PUBLISH request over UDP or TCP, using either a valid Content-Type: application/pidf+xml request or one with the header removed, and the vulnerable code path itself does not enforce authentication (though a deployment&amp;#39;s routing configuration may require it before this route is reached). The issue has been fixed in version 3.6.6 and 4.0.0-rc1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-45084</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-45084</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-45084</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: opensips&lt;/p&gt;
&lt;p&gt;OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module&amp;#39;s handle_publish() function processes a SIP PUBLISH request with an Event: presence header and a message body while the configuration option enable_sphere_check=1 is set, it invokes the get_content_type() macro without first calling parse_content_type_hdr(), causing it to dereference uninitialized or NULL Content-Type parsing state and crash. If a Content-Type header is present but unparsed, msg-&amp;gt;content_type-&amp;gt;parsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg-&amp;gt;content_type itself is NULL, and both cases lead to a crash. A remote attacker can therefore cause a denial of service against an affected instance with a single PUBLISH request over UDP or TCP, using either a valid Content-Type: application/pidf+xml request or one with the header removed, and the vulnerable code path itself does not enforce authentication (though a deployment&amp;#39;s routing configuration may require it before this route is reached). The issue has been fixed in version 3.6.6 and 4.0.0-rc1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: opensips&lt;/p&gt;
&lt;p&gt;OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module&amp;#39;s handle_publish() function processes a SIP PUBLISH request with an Event: presence header and a message body while the configuration option enable_sphere_check=1 is set, it invokes the get_content_type() macro without first calling parse_content_type_hdr(), causing it to dereference uninitialized or NULL Content-Type parsing state and crash. If a Content-Type header is present but unparsed, msg-&amp;gt;content_type-&amp;gt;parsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg-&amp;gt;content_type itself is NULL, and both cases lead to a crash. A remote attacker can therefore cause a denial of service against an affected instance with a single PUBLISH request over UDP or TCP, using either a valid Content-Type: application/pidf+xml request or one with the header removed, and the vulnerable code path itself does not enforce authentication (though a deployment&amp;#39;s routing configuration may require it before this route is reached). The issue has been fixed in version 3.6.6 and 4.0.0-rc1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-45084</guid>
    </item>
  </channel>
</rss>
