<?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 Tenable CBC Plugin Reporting With CTR Enabled in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5212954#M1116842</link>
    <description>&lt;P&gt;Hi cisco community,&lt;/P&gt;&lt;P&gt;I will admit i was not sure rather to put this under security or switching. Recently, my company has decided to have a outside auditor come in whom uses tenable. One of these scans has hit two of our switches, a 9300 and&amp;nbsp; 3560CX has having CBC enabled.&lt;/P&gt;&lt;P&gt;However both switches have confiqured as such:&lt;BR /&gt;(9300)&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;(3560)&amp;nbsp;&amp;nbsp;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Neither are using a CBC option. I asked for both to be ran again, and they both popped up positive again. I contacted tenable and was told to reach out to the vendor and ask for a security&amp;nbsp; patch.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried pushing everything on the switches to 512 but out corporate terminal client does not enjoy having the hostkey set that high.&lt;/P&gt;&lt;P&gt;The configs are as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;C9300-48U&lt;/P&gt;&lt;P&gt;ip ssh server authenticate user publickey&lt;BR /&gt;ip ssh server authenticate user keyboard&lt;BR /&gt;ip ssh server authenticate user password&lt;BR /&gt;no ip ssh server peruser session limit&lt;BR /&gt;ip ssh server certificate profile&lt;BR /&gt;ip ssh server algorithm mac hmac-sha2-512 hmac-sha2-256&lt;BR /&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;BR /&gt;ip ssh server algorithm kex curve25519-sha256@libssh.org ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group14-sha1&lt;BR /&gt;ip ssh server algorithm hostkey rsa-sha2-256 ssh-rsa&lt;BR /&gt;ip ssh server algorithm authentication publickey keyboard password&lt;BR /&gt;ip ssh server algorithm publickey x509v3-ssh-rsa ssh-rsa ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521 ssh-ed25519 x509v3-ecdsa-sha2-nistp256 x509v3-ecdsa-sha2-nistp384 x509v3-ecdsa-sha2-nistp521 rsa-sha2-256 rsa-sha2-512&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; WS-C3560CX-8PC-S&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip ssh server authenticate user publickey&lt;BR /&gt;ip ssh server authenticate user keyboard&lt;BR /&gt;ip ssh server authenticate user password&lt;BR /&gt;no ip ssh server peruser session limit&lt;BR /&gt;ip ssh server certificate profile&lt;BR /&gt;ip ssh server algorithm mac hmac-sha2-512 hmac-sha2-256&lt;BR /&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;BR /&gt;ip ssh server algorithm kex diffie-hellman-group14-sha1&lt;BR /&gt;ip ssh server algorithm hostkey x509v3-ssh-rsa ssh-rsa&lt;BR /&gt;ip ssh server algorithm authentication publickey keyboard password&lt;BR /&gt;ip ssh server algorithm publickey x509v3-ssh-rsa ssh-rsa&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there another setting i am missing which would effect this hit? The plugin text is:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;The SSH server is configured to support Cipher Block Chaining (CBC) encryption.&amp;nbsp; This may allow an attacker to recover the plaintext message from the ciphertext."&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Thank you for your assistance!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 22 Oct 2024 13:51:01 GMT</pubDate>
    <dc:creator>jbulloch</dc:creator>
    <dc:date>2024-10-22T13:51:01Z</dc:date>
    <item>
      <title>Tenable CBC Plugin Reporting With CTR Enabled</title>
      <link>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5212954#M1116842</link>
      <description>&lt;P&gt;Hi cisco community,&lt;/P&gt;&lt;P&gt;I will admit i was not sure rather to put this under security or switching. Recently, my company has decided to have a outside auditor come in whom uses tenable. One of these scans has hit two of our switches, a 9300 and&amp;nbsp; 3560CX has having CBC enabled.&lt;/P&gt;&lt;P&gt;However both switches have confiqured as such:&lt;BR /&gt;(9300)&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;&lt;SPAN class=""&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;(3560)&amp;nbsp;&amp;nbsp;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Neither are using a CBC option. I asked for both to be ran again, and they both popped up positive again. I contacted tenable and was told to reach out to the vendor and ask for a security&amp;nbsp; patch.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried pushing everything on the switches to 512 but out corporate terminal client does not enjoy having the hostkey set that high.&lt;/P&gt;&lt;P&gt;The configs are as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;C9300-48U&lt;/P&gt;&lt;P&gt;ip ssh server authenticate user publickey&lt;BR /&gt;ip ssh server authenticate user keyboard&lt;BR /&gt;ip ssh server authenticate user password&lt;BR /&gt;no ip ssh server peruser session limit&lt;BR /&gt;ip ssh server certificate profile&lt;BR /&gt;ip ssh server algorithm mac hmac-sha2-512 hmac-sha2-256&lt;BR /&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;BR /&gt;ip ssh server algorithm kex curve25519-sha256@libssh.org ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group14-sha1&lt;BR /&gt;ip ssh server algorithm hostkey rsa-sha2-256 ssh-rsa&lt;BR /&gt;ip ssh server algorithm authentication publickey keyboard password&lt;BR /&gt;ip ssh server algorithm publickey x509v3-ssh-rsa ssh-rsa ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521 ssh-ed25519 x509v3-ecdsa-sha2-nistp256 x509v3-ecdsa-sha2-nistp384 x509v3-ecdsa-sha2-nistp521 rsa-sha2-256 rsa-sha2-512&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; WS-C3560CX-8PC-S&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ip ssh server authenticate user publickey&lt;BR /&gt;ip ssh server authenticate user keyboard&lt;BR /&gt;ip ssh server authenticate user password&lt;BR /&gt;no ip ssh server peruser session limit&lt;BR /&gt;ip ssh server certificate profile&lt;BR /&gt;ip ssh server algorithm mac hmac-sha2-512 hmac-sha2-256&lt;BR /&gt;ip ssh server algorithm encryption aes256-ctr aes192-ctr aes128-ctr&lt;BR /&gt;ip ssh server algorithm kex diffie-hellman-group14-sha1&lt;BR /&gt;ip ssh server algorithm hostkey x509v3-ssh-rsa ssh-rsa&lt;BR /&gt;ip ssh server algorithm authentication publickey keyboard password&lt;BR /&gt;ip ssh server algorithm publickey x509v3-ssh-rsa ssh-rsa&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there another setting i am missing which would effect this hit? The plugin text is:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;The SSH server is configured to support Cipher Block Chaining (CBC) encryption.&amp;nbsp; This may allow an attacker to recover the plaintext message from the ciphertext."&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Thank you for your assistance!&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2024 13:51:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5212954#M1116842</guid>
      <dc:creator>jbulloch</dc:creator>
      <dc:date>2024-10-22T13:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Tenable CBC Plugin Reporting With CTR Enabled</title>
      <link>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5213412#M1116865</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - You can verify the enabled ciphers with :&amp;nbsp; &amp;nbsp;%&amp;nbsp;&lt;STRONG&gt;nmap --script ssh2-enum-algos&amp;nbsp; switchname&lt;BR /&gt;&lt;/STRONG&gt;&amp;nbsp; &amp;nbsp; (nmap.org)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 06:45:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5213412#M1116865</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-23T06:45:01Z</dc:date>
    </item>
    <item>
      <title>Re: Tenable CBC Plugin Reporting With CTR Enabled</title>
      <link>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5214684#M1116946</link>
      <description>&lt;P&gt;marce,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the input and while that is helpful i cannot run nmap in our environment.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 18:38:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5214684#M1116946</guid>
      <dc:creator>jbulloch</dc:creator>
      <dc:date>2024-10-24T18:38:56Z</dc:date>
    </item>
    <item>
      <title>Re: Tenable CBC Plugin Reporting With CTR Enabled</title>
      <link>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5214689#M1116948</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;- The feeling around that argument is something I defy ; you &lt;BR /&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;'don't run nmap in your environmen&lt;/EM&gt;t' ;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; you run a command as a&amp;nbsp; technical authorized administrator on a&lt;EM&gt; single&lt;/EM&gt; device to examine an issue.&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Or what about all your other users who might have downloaded it already , and scanned&amp;nbsp; your&lt;BR /&gt;&amp;nbsp; &amp;nbsp; network numerous times.....-&amp;gt;?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 18:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tenable-cbc-plugin-reporting-with-ctr-enabled/m-p/5214689#M1116948</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-24T18:48:18Z</dc:date>
    </item>
  </channel>
</rss>

