<?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>article VA scan shows LUCKY13 Vulnerability for our Managed component in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/VA-scan-shows-LUCKY13-Vulnerability-for-our-Managed-component/ta-p/242425</link>
    <description>&lt;H2&gt;Self Service Summary&lt;/H2&gt;
&lt;P&gt;Some customers have detected exposure to the "&lt;STRONG&gt;LUCKY13 Vulnerability attack&lt;/STRONG&gt;" in their VA scans for our Managed component.&lt;BR /&gt;Also known as &lt;A title="CVE-2013-0169" href="https://nvd.nist.gov/vuln/detail/CVE-2013-0169" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;CVE-2013-0169&lt;/STRONG&gt;&lt;/A&gt;, this vulnerability has been analyzed and fixed.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;We are not affected&lt;/STRONG&gt;, there is no risk that the “Lucky13” can be exploited on our systems.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;Issue&lt;/TD&gt;
&lt;TD&gt;Solution&lt;/TD&gt;
&lt;TD&gt;Tasks&lt;/TD&gt;
&lt;TD&gt;Alternative(s)&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="187.716px"&gt;LUCKY13 Vulnerability attack&lt;/TD&gt;
&lt;TD width="74.9091px"&gt;We are not affected.&lt;/TD&gt;
&lt;TD width="148.739px"&gt;&lt;SPAN&gt;Check below information and explain it to your Security Team&lt;/SPAN&gt;&lt;/TD&gt;
&lt;TD width="399.545px"&gt;
&lt;P&gt;&lt;SPAN&gt;The implementations used by Dynatrace are all up to date and contain the corresponding patches.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please submit a Support ticket if you have additional questions or concerns.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The use of cipher suites for TLS that operate in CBC mode can be considered an issue if the underlying implementation is not protected against this kind of attack.&lt;/P&gt;
&lt;P&gt;The “Lucky13” timing attack was found in 2013 and, as also stated in NVD - CVE-2013-0169, has since been mitigated in several libraries like: OpenSSL, PolarSSL, Mozilla NSS, gnuTLS, BouncyCastle, and basically all other industry-relevant libraries used for cryptographic purposes.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Apr 2024 15:12:21 GMT</pubDate>
    <dc:creator>LucaGalliani</dc:creator>
    <dc:date>2024-04-17T15:12:21Z</dc:date>
    <item>
      <title>VA scan shows LUCKY13 Vulnerability for our Managed component</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/VA-scan-shows-LUCKY13-Vulnerability-for-our-Managed-component/ta-p/242425</link>
      <description>&lt;H2&gt;Self Service Summary&lt;/H2&gt;
&lt;P&gt;Some customers have detected exposure to the "&lt;STRONG&gt;LUCKY13 Vulnerability attack&lt;/STRONG&gt;" in their VA scans for our Managed component.&lt;BR /&gt;Also known as &lt;A title="CVE-2013-0169" href="https://nvd.nist.gov/vuln/detail/CVE-2013-0169" target="_blank" rel="noopener"&gt;&lt;STRONG&gt;CVE-2013-0169&lt;/STRONG&gt;&lt;/A&gt;, this vulnerability has been analyzed and fixed.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;We are not affected&lt;/STRONG&gt;, there is no risk that the “Lucky13” can be exploited on our systems.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;Issue&lt;/TD&gt;
&lt;TD&gt;Solution&lt;/TD&gt;
&lt;TD&gt;Tasks&lt;/TD&gt;
&lt;TD&gt;Alternative(s)&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="187.716px"&gt;LUCKY13 Vulnerability attack&lt;/TD&gt;
&lt;TD width="74.9091px"&gt;We are not affected.&lt;/TD&gt;
&lt;TD width="148.739px"&gt;&lt;SPAN&gt;Check below information and explain it to your Security Team&lt;/SPAN&gt;&lt;/TD&gt;
&lt;TD width="399.545px"&gt;
&lt;P&gt;&lt;SPAN&gt;The implementations used by Dynatrace are all up to date and contain the corresponding patches.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please submit a Support ticket if you have additional questions or concerns.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The use of cipher suites for TLS that operate in CBC mode can be considered an issue if the underlying implementation is not protected against this kind of attack.&lt;/P&gt;
&lt;P&gt;The “Lucky13” timing attack was found in 2013 and, as also stated in NVD - CVE-2013-0169, has since been mitigated in several libraries like: OpenSSL, PolarSSL, Mozilla NSS, gnuTLS, BouncyCastle, and basically all other industry-relevant libraries used for cryptographic purposes.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2024 15:12:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/VA-scan-shows-LUCKY13-Vulnerability-for-our-Managed-component/ta-p/242425</guid>
      <dc:creator>LucaGalliani</dc:creator>
      <dc:date>2024-04-17T15:12:21Z</dc:date>
    </item>
  </channel>
</rss>

