<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FWSM multi-context and vulnerabilities in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-multi-context-and-vulnerabilities/m-p/1606835#M559795</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a query regarding FWSM blade operation in multi-context mode and vulnerabilities. FWSM OS version is 3.2(18). This version is vulnerable to Cisco bug ID &lt;A href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCtl84952" style="word-break: break-all;" target="_blank"&gt;&lt;STRONG&gt;CSCtl84952&lt;/STRONG&gt;&lt;/A&gt;. Only one of the context uses SCCP inspection . As per Cisco site successful exploitation of this vulnerability may cause a reload of the affected device. Repeated exploitation could result in a sustained denial of service condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can successfull exploitation of this vulnerabilty in a normal context result in impact to the FWSM module as a whole ( i.e. all the other contexts)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vijay Sequeira&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 20:07:52 GMT</pubDate>
    <dc:creator>vaibhav.gurav</dc:creator>
    <dc:date>2019-03-11T20:07:52Z</dc:date>
    <item>
      <title>FWSM multi-context and vulnerabilities</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-multi-context-and-vulnerabilities/m-p/1606835#M559795</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a query regarding FWSM blade operation in multi-context mode and vulnerabilities. FWSM OS version is 3.2(18). This version is vulnerable to Cisco bug ID &lt;A href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCtl84952" style="word-break: break-all;" target="_blank"&gt;&lt;STRONG&gt;CSCtl84952&lt;/STRONG&gt;&lt;/A&gt;. Only one of the context uses SCCP inspection . As per Cisco site successful exploitation of this vulnerability may cause a reload of the affected device. Repeated exploitation could result in a sustained denial of service condition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can successfull exploitation of this vulnerabilty in a normal context result in impact to the FWSM module as a whole ( i.e. all the other contexts)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vijay Sequeira&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:07:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-multi-context-and-vulnerabilities/m-p/1606835#M559795</guid>
      <dc:creator>vaibhav.gurav</dc:creator>
      <dc:date>2019-03-11T20:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM multi-context and vulnerabilities</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-multi-context-and-vulnerabilities/m-p/1606836#M559796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, if the vulnerability was exploited in one context, the entire firewall module would reload. This would affect other traffic flowing through other contexts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should schedule an upgrade to the latest 3.2.x maintenance release when possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Mar 2011 16:18:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-multi-context-and-vulnerabilities/m-p/1606836#M559796</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2011-03-16T16:18:31Z</dc:date>
    </item>
  </channel>
</rss>

