<?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 ISE 2.6 Vulnerability - Web Server TLS BREACH Attack in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-6-vulnerability-web-server-tls-breach-attack/m-p/4440655#M568759</link>
    <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a client, with this vulnerability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Vulnerability title: Web Server TLS BREACH Attack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;* By observing the length of compressed HTTPS responses, an attacker may be able to derive plaintext secrets from the ciphertext of an HTTPS stream.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Solution presented:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently unaware of a practical solution to this problem. Please consider the following workarounds.&lt;/P&gt;&lt;P&gt;Some of these mitigations may protect entire applications, while others may only protect individual web pages.&lt;/P&gt;&lt;P&gt;- Disable HTTP compression.&lt;BR /&gt;- Separate the secrets from the user input.&lt;BR /&gt;- Randomize the secrets in each client request.&lt;BR /&gt;- Mask secrets (effectively randomizing by XORing with a random secret per request).&lt;BR /&gt;- Protect web pages from CSRF attacks.&lt;BR /&gt;- Obfuscate the length of web responses by adding random amounts of arbitrary bytes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to apply this workaround on cisco ISE?&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jul 2021 20:50:23 GMT</pubDate>
    <dc:creator>Ricardo Matias Aires</dc:creator>
    <dc:date>2021-07-28T20:50:23Z</dc:date>
    <item>
      <title>ISE 2.6 Vulnerability - Web Server TLS BREACH Attack</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-6-vulnerability-web-server-tls-breach-attack/m-p/4440655#M568759</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a client, with this vulnerability.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Vulnerability title: Web Server TLS BREACH Attack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;* By observing the length of compressed HTTPS responses, an attacker may be able to derive plaintext secrets from the ciphertext of an HTTPS stream.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Solution presented:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are currently unaware of a practical solution to this problem. Please consider the following workarounds.&lt;/P&gt;&lt;P&gt;Some of these mitigations may protect entire applications, while others may only protect individual web pages.&lt;/P&gt;&lt;P&gt;- Disable HTTP compression.&lt;BR /&gt;- Separate the secrets from the user input.&lt;BR /&gt;- Randomize the secrets in each client request.&lt;BR /&gt;- Mask secrets (effectively randomizing by XORing with a random secret per request).&lt;BR /&gt;- Protect web pages from CSRF attacks.&lt;BR /&gt;- Obfuscate the length of web responses by adding random amounts of arbitrary bytes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to apply this workaround on cisco ISE?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jul 2021 20:50:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-6-vulnerability-web-server-tls-breach-attack/m-p/4440655#M568759</guid>
      <dc:creator>Ricardo Matias Aires</dc:creator>
      <dc:date>2021-07-28T20:50:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.6 Vulnerability - Web Server TLS BREACH Attack</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-6-vulnerability-web-server-tls-breach-attack/m-p/4440706#M568761</link>
      <description>&lt;P&gt;There is no access to the underlying OS in ISE, so you cannot make changes to the web server to apply these mitigations.&lt;/P&gt;
&lt;P&gt;Is this vulnerability linked to a known CVE? If so, you can check if it is a known vulnerability in Cisco products via the &lt;A href="https://tools.cisco.com/security/center/publicationListing.x" target="_blank" rel="noopener"&gt;Security Advisories&lt;/A&gt; page.&lt;/P&gt;
&lt;P&gt;If this is not a known vulnerability and you have a detailed vulnerability report, you can submit it to the Cisco PSIRT team for review as per the &lt;A href="https://tools.cisco.com/security/center/resources/security_vulnerability_policy.html" target="_blank" rel="noopener"&gt;Security Vulnerability Policy&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;As with other vulnerabilities related to the Web UI, you can mitigate the risk of a threat actor exploiting this vulnerability by limiting access to the Web UI to specific source management IPs/VLANs using the &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_30_basic_setup.html?bookSearch=true#ID626" target="_blank" rel="noopener"&gt;IP Access Restrictions&lt;/A&gt; list.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jul 2021 23:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-6-vulnerability-web-server-tls-breach-attack/m-p/4440706#M568761</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2021-07-28T23:38:44Z</dc:date>
    </item>
  </channel>
</rss>

