<?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: Cisco ISE with AD CVE-2022-38023 patch in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4733697#M578677</link>
    <description>&lt;P&gt;&amp;gt; ISE 2.x currently only supports RC4 with AD...&lt;/P&gt;
&lt;P&gt;This statement is incorrect. AFAIK the issue is usually due to some element in the AD infrastructure is still using RC4 and tells ISE to communicate with RC4 as the etype. Customers thought the issue would have gone away if ISE did not support RC4 at all.&lt;/P&gt;
&lt;P&gt;These articles might interest you:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/decrypting-the-selection-of-supported-kerberos-encryption-types/ba-p/1628797" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/decrypting-the-selection-of-supported-kerberos-encryption-types/ba-p/1628797&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/troubleshooting-kerberos-authentication-problems-8211-name/ba-p/395288" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/troubleshooting-kerberos-authentication-problems-8211-name/ba-p/395288&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/itops-talk-blog/tough-questions-answered-can-i-disable-rc4-etype-for-kerberos-on/ba-p/382718" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/itops-talk-blog/tough-questions-answered-can-i-disable-rc4-etype-for-kerberos-on/ba-p/382718&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain#resolution" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain#resolution&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Sat, 10 Dec 2022 19:58:11 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2022-12-10T19:58:11Z</dc:date>
    <item>
      <title>Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4726688#M578449</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have an ISE 2.7 patch 7 distributed deployment that is bound to AD.&lt;/P&gt;&lt;P&gt;AD was recently patched with regards to CVE-2022-38023. Since then, the AD admins are reporting that the PSNs are appearing in their logs every few hours with "The Netlogon service encountered a client using RPC signing instead of RPC sealing)."&lt;/P&gt;&lt;P&gt;I've tried to replicate the issue with a Test User Authentication from ISE with Authentication Type set to Kerberos but this doesn't appear in the AD logs with the error. Has anyone else experienced this behaviour with ISE and AD patched for CVE-2022-38023?&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Andy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Microsoft Knowledgebase on issue is below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/topic/kb5021130-how-to-manage-the-netlogon-protocol-changes-related-to-cve-2022-38023-46ea3067-3989-4d40-963c-680fd9e8ee25" target="_blank"&gt;https://support.microsoft.com/en-us/topic/kb5021130-how-to-manage-the-netlogon-protocol-changes-related-to-cve-2022-38023-46ea3067-3989-4d40-963c-680fd9e8ee25&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 15:32:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4726688#M578449</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2022-11-23T15:32:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4730278#M578563</link>
      <description>&lt;P&gt;The AD admins confirmed that the PSN generated event ID in their logs was actually:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;event id: 5840: The Netlogon service created a secure channel with a client with RC4.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I found the following cisco ISE bug:&lt;/P&gt;&lt;P&gt;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvv82074" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvv82074&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From my reading of both the Cisco bug and the MS knowledgebase article, it looks like I'll run into the Cisco bug when the AD CVE-2022-38023 patch goes into its enforcement phase in April 2023. I've opened a TAC case to confirm.&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 30 Nov 2022 12:32:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4730278#M578563</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2022-11-30T12:32:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4732636#M578644</link>
      <description>&lt;P&gt;Contacted TAC - Cisco were already aware of this issue. Enhancement below was logged to deal with this.&lt;/P&gt;&lt;P&gt;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvo60450" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvo60450&lt;/A&gt;&lt;/P&gt;&lt;P&gt;ISE 2.x currently only supports RC4 with AD - the above enhancement changes this to AES256. Will probably upgrade to ISE 3.x rather than wait for the 2.x patch.&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 05 Dec 2022 15:23:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4732636#M578644</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2022-12-05T15:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4733697#M578677</link>
      <description>&lt;P&gt;&amp;gt; ISE 2.x currently only supports RC4 with AD...&lt;/P&gt;
&lt;P&gt;This statement is incorrect. AFAIK the issue is usually due to some element in the AD infrastructure is still using RC4 and tells ISE to communicate with RC4 as the etype. Customers thought the issue would have gone away if ISE did not support RC4 at all.&lt;/P&gt;
&lt;P&gt;These articles might interest you:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/decrypting-the-selection-of-supported-kerberos-encryption-types/ba-p/1628797" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/decrypting-the-selection-of-supported-kerberos-encryption-types/ba-p/1628797&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/troubleshooting-kerberos-authentication-problems-8211-name/ba-p/395288" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/troubleshooting-kerberos-authentication-problems-8211-name/ba-p/395288&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/t5/itops-talk-blog/tough-questions-answered-can-i-disable-rc4-etype-for-kerberos-on/ba-p/382718" target="_blank" rel="noopener"&gt;https://techcommunity.microsoft.com/t5/itops-talk-blog/tough-questions-answered-can-i-disable-rc4-etype-for-kerberos-on/ba-p/382718&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain#resolution" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/unsupported-etype-error-accessing-trusted-domain#resolution&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Sat, 10 Dec 2022 19:58:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4733697#M578677</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2022-12-10T19:58:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4733877#M578682</link>
      <description>&lt;P&gt;Thanks for the clarification and links - much appreciated.&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 09:04:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4733877#M578682</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2022-12-07T09:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4771442#M579724</link>
      <description>&lt;P&gt;Hi andrewswanson,&lt;/P&gt;&lt;P&gt;We have the exact same issue as reported above, I've see the link to this bug :&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvo60450" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvo60450&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But as far as I can tell there is no version of ISE that is currently listed as a known fixed release. How did you manage to get this resolved?&lt;/P&gt;&lt;P&gt;Many thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 15:29:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4771442#M579724</guid>
      <dc:creator>samdejongh</dc:creator>
      <dc:date>2023-02-08T15:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4771449#M579725</link>
      <description>&lt;P&gt;Hi - Still not resolved this as TAC recommended to upgrade to 3.X. will hopefully get this done in the next few months.&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 15:44:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4771449#M579725</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2023-02-08T15:44:20Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4798485#M580649</link>
      <description>&lt;P&gt;Hi hslai,&lt;/P&gt;
&lt;P&gt;so if I understand it correctly. The Cisco ISE 2.7 (Patch8 in my Case) should still be able to communicate with the AD if the AD-Element uses the AES etype and tells the ISE to comunicate with it ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2023 11:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4798485#M580649</guid>
      <dc:creator>Niko99</dc:creator>
      <dc:date>2023-03-21T11:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE with AD CVE-2022-38023 patch</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4800779#M580732</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I disabled RC4 in AD object for one of my ISE but eventID 5840:&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;The Netlogon service created a secure channel with a client with RC4.&lt;/STRONG&gt;&lt;/EM&gt; still are generating.&amp;nbsp;&lt;BR /&gt;ISE version &lt;SPAN class=""&gt;003.000(000.458)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Krzysztof&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 11:42:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-with-ad-cve-2022-38023-patch/m-p/4800779#M580732</guid>
      <dc:creator>maziek</dc:creator>
      <dc:date>2023-03-24T11:42:13Z</dc:date>
    </item>
  </channel>
</rss>

