<?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>Tue, 10 Nov 2026 09:28:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-12067</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-12067</link>
      <description>&lt;p&gt;Missing exception handlers in AvastSvc native message dispatcher (ashServ.dll) on Windows allow a local, unprivileged attacker to crash the service by sending specially crafted JSON messages.&lt;/p&gt;
&lt;p&gt;The vulnerability spans multiple handler pathways in the RPC-based native message protocol:&lt;/p&gt;
&lt;p&gt;*  Log_NmSvc.message handler: converts JSON fields to strings without type validation and without exception boundaries. 
  *  OpenInSz_NmSvc handler: converts URL and origin fields to strings without type checking, exposing an exception.
  *  OpenInSz_NmSvc.profile handler: converts the profile field to an integer without validation.&lt;/p&gt;
&lt;p&gt;In all three cases, the exceptions are not caught by action-specific handlers and propagate up the dispatcher. The common root cause is the absence of try-catch blocks around JSON type conversions in the native message processing chain.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Missing exception handlers in AvastSvc native message dispatcher (ashServ.dll) on Windows allow a local, unprivileged attacker to crash the service by sending specially crafted JSON messages.&lt;/p&gt;
&lt;p&gt;The vulnerability spans multiple handler pathways in the RPC-based native message protocol:&lt;/p&gt;
&lt;p&gt;*  Log_NmSvc.message handler: converts JSON fields to strings without type validation and without exception boundaries. 
  *  OpenInSz_NmSvc handler: converts URL and origin fields to strings without type checking, exposing an exception.
  *  OpenInSz_NmSvc.profile handler: converts the profile field to an integer without validation.&lt;/p&gt;
&lt;p&gt;In all three cases, the exceptions are not caught by action-specific handlers and propagate up the dispatcher. The common root cause is the absence of try-catch blocks around JSON type conversions in the native message processing chain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-12067</guid>
    </item>
    <item>
      <title>GHSA-fpp4-5g35-6qq3</title>
      <link>https://db.gcve.eu/vuln/ghsa-fpp4-5g35-6qq3</link>
      <description>&lt;p&gt;Missing exception handlers in AvastSvc native message dispatcher (ashServ.dll) on Windows allow a local, unprivileged attacker to crash the service by sending specially crafted JSON messages.&lt;/p&gt;
&lt;p&gt;The vulnerability spans multiple handler pathways in the RPC-based native message protocol:&lt;/p&gt;
&lt;p&gt;*  Log_NmSvc.message handler: converts JSON fields to strings without type validation and without exception boundaries. 
  *  OpenInSz_NmSvc handler: converts URL and origin fields to strings without type checking, exposing an exception.
  *  OpenInSz_NmSvc.profile handler: converts the profile field to an integer without validation.&lt;/p&gt;
&lt;p&gt;In all three cases, the exceptions are not caught by action-specific handlers and propagate up the dispatcher. The common root cause is the absence of try-catch blocks around JSON type conversions in the native message processing chain.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Missing exception handlers in AvastSvc native message dispatcher (ashServ.dll) on Windows allow a local, unprivileged attacker to crash the service by sending specially crafted JSON messages.&lt;/p&gt;
&lt;p&gt;The vulnerability spans multiple handler pathways in the RPC-based native message protocol:&lt;/p&gt;
&lt;p&gt;*  Log_NmSvc.message handler: converts JSON fields to strings without type validation and without exception boundaries. 
  *  OpenInSz_NmSvc handler: converts URL and origin fields to strings without type checking, exposing an exception.
  *  OpenInSz_NmSvc.profile handler: converts the profile field to an integer without validation.&lt;/p&gt;
&lt;p&gt;In all three cases, the exceptions are not caught by action-specific handlers and propagate up the dispatcher. The common root cause is the absence of try-catch blocks around JSON type conversions in the native message processing chain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fpp4-5g35-6qq3</guid>
    </item>
  </channel>
</rss>
