<?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 Re: SSID Confusion attack in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493007#M299230</link>
    <description>&lt;P&gt;There is no public bug or PSIRT for this vulnerability yet, given it's still pretty fresh.&lt;/P&gt;&lt;P&gt;Raise a support ticket for more information as they may already be investigating internally.&lt;/P&gt;</description>
    <pubDate>Thu, 30 May 2024 00:47:02 GMT</pubDate>
    <dc:creator>Brash</dc:creator>
    <dc:date>2024-05-30T00:47:02Z</dc:date>
    <item>
      <title>SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493000#M299223</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would like to know if Meraki has some taken any steps to mitigate this vulnerability.&lt;/P&gt;&lt;P&gt;We are:&lt;BR /&gt;- using WPA2 encryption and not WPA3&lt;BR /&gt;- using RADIUS authentication&lt;/P&gt;&lt;P&gt;I hope Meraki will release a patch to mitigate the vulnerability. Does anyone know or shed some light on the steps that Meraki is going to take or is advising the customers ?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 19:56:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493000#M299223</guid>
      <dc:creator>gagandeep singh3</dc:creator>
      <dc:date>2024-05-29T19:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493001#M299224</link>
      <description>&lt;P&gt;What vulnerability? Do you have the CVE?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 19:58:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493001#M299224</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2024-05-29T19:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493002#M299225</link>
      <description>&lt;H3 id="toc-hId-1451047744"&gt;SSID Confusion Attack WiFi Vulnerability (CVE-2023-52424)&lt;/H3&gt;</description>
      <pubDate>Wed, 29 May 2024 20:00:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493002#M299225</guid>
      <dc:creator>gagandeep singh3</dc:creator>
      <dc:date>2024-05-29T20:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493003#M299226</link>
      <description>&lt;P&gt;This CVE is from 2023, Meraki has probably already released the fix some time ago, as they frequently release new updates.&lt;/P&gt;&lt;P&gt;Have you already contacted support?&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 20:06:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493003#M299226</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2024-05-29T20:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493004#M299227</link>
      <description>&lt;P&gt;Doubt that Meraki has published a fix for that. The CVE was published this month.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 20:13:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493004#M299227</guid>
      <dc:creator>Raphael_L</dc:creator>
      <dc:date>2024-05-29T20:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493005#M299228</link>
      <description>&lt;P&gt;Without knowing exactly what the underlying mechanisms is in this specific CVE, from what I'm reading about it, it's simply an overall design flaw in the 802.11 standard.&lt;/P&gt;&lt;P&gt;It's always been there, and will always be there.&lt;/P&gt;&lt;P&gt;Basically it aims at tricking a user to associate to your malicious and less secure SSID (a honeypot) and eavesdrop on all your traffic.&lt;/P&gt;&lt;P&gt;If you really want to mitigate it, there's an easy fix.&lt;/P&gt;&lt;P&gt;Turn of all your WiFi and Access Points, and cable your devices to the network.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 21:10:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493005#M299228</guid>
      <dc:creator>Rasmus Hoffmann Birkelund</dc:creator>
      <dc:date>2024-05-29T21:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493006#M299229</link>
      <description>&lt;P&gt;It's a day old I doubt any vendor has patched it as it's still being analysed. &lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2024 23:30:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493006#M299229</guid>
      <dc:creator>BlakeRichardson</dc:creator>
      <dc:date>2024-05-29T23:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493007#M299230</link>
      <description>&lt;P&gt;There is no public bug or PSIRT for this vulnerability yet, given it's still pretty fresh.&lt;/P&gt;&lt;P&gt;Raise a support ticket for more information as they may already be investigating internally.&lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2024 00:47:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493007#M299230</guid>
      <dc:creator>Brash</dc:creator>
      <dc:date>2024-05-30T00:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493008#M299231</link>
      <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/108862"&gt;@gagandeep singh3&lt;/A&gt;, &lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;EM&gt;&lt;STRONG&gt;NOTE: I DO NOT KNOW, THE FULL INS AND OUTS OF THIS VULNERABILITY.&lt;/STRONG&gt; &lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;That said, Meraki Air Marshal does have some level of mitigation from Rouge SSIDs. See below guide for further details.&lt;/P&gt;&lt;P&gt;&lt;A href="https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Monitoring_and_Reporting/Air_Marshal&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2024 00:58:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493008#M299231</guid>
      <dc:creator>IvanJukic</dc:creator>
      <dc:date>2024-05-30T00:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: SSID Confusion attack</title>
      <link>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493009#M299232</link>
      <description>&lt;P&gt;Original writeup came out a few weeks ago: &lt;A href="https://www.top10vpn.com/research/wifi-vulnerability-ssid" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.top10vpn.com/research/wifi-vulnerability-ssid&lt;/A&gt;/&lt;/P&gt;&lt;P&gt;I wouldn't expect a fix to be released quickly, if at all!&lt;/P&gt;</description>
      <pubDate>Thu, 30 May 2024 03:20:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ssid-confusion-attack/m-p/5493009#M299232</guid>
      <dc:creator>Paccers</dc:creator>
      <dc:date>2024-05-30T03:20:06Z</dc:date>
    </item>
  </channel>
</rss>

