<?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: Microsoft CVE-2022-38023 and NTLMv2 in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Microsoft-CVE-2022-38023-and-NTLMv2/m-p/445829#M9891</link>
    <description>&lt;P&gt;Enhancement in ONTAP release such as 9.13.1 (to address CVE-2022-38023) does &lt;STRONG&gt;not&lt;/STRONG&gt; close NTLMv2 authentication, rather it allows it pass through without 'access denied' error. Basically, if you DO NOT upgrade to the fixed_ontap_release, then after July 11, all the NTLMv2 auth-users will be access denied.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jul 2023 22:56:46 GMT</pubDate>
    <dc:creator>Ontapforrum</dc:creator>
    <dc:date>2023-07-07T22:56:46Z</dc:date>
    <item>
      <title>Microsoft CVE-2022-38023 and NTLMv2</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Microsoft-CVE-2022-38023-and-NTLMv2/m-p/445828#M9890</link>
      <description>&lt;DIV&gt;We've upgraded our AFF-A220 to 9.13.1 as perNetApp's SU530&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;and should be all good to go for next Tuesday's closing of the door on NTLMv2 authentication.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;However,&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;scrb::&amp;gt; vserver cifs session show -vserver sdata -fields auth-mechanism,address,windows-user&lt;BR /&gt;node &amp;nbsp; &amp;nbsp; vserver &amp;nbsp; &amp;nbsp;session-id &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; connection-id address &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; auth-mechanism windows-user&lt;BR /&gt;-------- ---------- -------------------- ------------- --------------- -------------- ------------&lt;BR /&gt;scrb-a sdata &amp;nbsp; &amp;nbsp; &amp;nbsp;12223613813613660030 4271015427 &amp;nbsp; &amp;nbsp;10.6.154.156 &amp;nbsp; &amp;nbsp;NTLMv2 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; FHC\rgrasdue&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;still shows all of our CIFS connections using NTLMv2 to authenticate (one line is shown of hundreds of connections)&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Are we ready for next week's update? Will the auth-mechanism change after we patch our DCs? Or will all our CIFS connections break?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 04 Jun 2025 09:47:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Microsoft-CVE-2022-38023-and-NTLMv2/m-p/445828#M9890</guid>
      <dc:creator>RandyRue</dc:creator>
      <dc:date>2025-06-04T09:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: Microsoft CVE-2022-38023 and NTLMv2</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Microsoft-CVE-2022-38023-and-NTLMv2/m-p/445829#M9891</link>
      <description>&lt;P&gt;Enhancement in ONTAP release such as 9.13.1 (to address CVE-2022-38023) does &lt;STRONG&gt;not&lt;/STRONG&gt; close NTLMv2 authentication, rather it allows it pass through without 'access denied' error. Basically, if you DO NOT upgrade to the fixed_ontap_release, then after July 11, all the NTLMv2 auth-users will be access denied.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jul 2023 22:56:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Microsoft-CVE-2022-38023-and-NTLMv2/m-p/445829#M9891</guid>
      <dc:creator>Ontapforrum</dc:creator>
      <dc:date>2023-07-07T22:56:46Z</dc:date>
    </item>
  </channel>
</rss>

