<?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: CVE-2023-51385 and CVE-2023-38408 in Runtime 17.3 LTS in Azure Gov Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151985#M53734</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143601"&gt;@moto-charles&lt;/a&gt;,&lt;/P&gt;
&lt;P class="wnfdntd" data-pm-slice="1 1 []"&gt;For an authoritative statement on CVE‑2023‑51385 and CVE‑2023‑38408 in your specific workspace and region (Azure Gov), the best path is to open a support ticket from your Azure Databricks workspace. That allows Databricks Support and Security to&amp;nbsp;&lt;SPAN&gt;confirm the applicability of these specific CVEs to your configuration and images, and&amp;nbsp;to&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;provide concrete guidance on risk and on any recommended maintenance update or runtime upgrade path.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="wnfdntd"&gt;That way, you get an official answer that your security team can rely on for their assessment and documentation. The community&lt;SPAN&gt;&amp;nbsp;cannot reliably provide this confirmation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P class="wnfdntd"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Mar 2026 10:31:55 GMT</pubDate>
    <dc:creator>Ashwin_DSA</dc:creator>
    <dc:date>2026-03-25T10:31:55Z</dc:date>
    <item>
      <title>CVE-2023-51385 and CVE-2023-38408 in Runtime 17.3 LTS in Azure Gov Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151178#M53609</link>
      <description>&lt;P&gt;My org is running Databricks in Azure Gov and recently upgraded from runtime 17.1 to 17.3 LTS.&amp;nbsp; Around the same time as the upgrade, our security team found 17 CVE's, two of which are related to openssh.&amp;nbsp; We have already contacted Microsoft and they stated Databricks needed to update the images to use a more recent version of openssh.&amp;nbsp; Databricks can you confirm this and possibly resolve the CVEs in Azure Gov Databricks?&amp;nbsp; Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2026 19:22:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151178#M53609</guid>
      <dc:creator>moto-charles</dc:creator>
      <dc:date>2026-03-17T19:22:19Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-51385 and CVE-2023-38408 in Runtime 17.3 LTS in Azure Gov Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151179#M53610</link>
      <description>&lt;P&gt;&lt;SPAN&gt;CVE-2023-51385 and CVE-2023-38408&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2026 19:22:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151179#M53610</guid>
      <dc:creator>moto-charles</dc:creator>
      <dc:date>2026-03-17T19:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: CVE-2023-51385 and CVE-2023-38408 in Runtime 17.3 LTS in Azure Gov Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151985#M53734</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143601"&gt;@moto-charles&lt;/a&gt;,&lt;/P&gt;
&lt;P class="wnfdntd" data-pm-slice="1 1 []"&gt;For an authoritative statement on CVE‑2023‑51385 and CVE‑2023‑38408 in your specific workspace and region (Azure Gov), the best path is to open a support ticket from your Azure Databricks workspace. That allows Databricks Support and Security to&amp;nbsp;&lt;SPAN&gt;confirm the applicability of these specific CVEs to your configuration and images, and&amp;nbsp;to&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;provide concrete guidance on risk and on any recommended maintenance update or runtime upgrade path.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="wnfdntd"&gt;That way, you get an official answer that your security team can rely on for their assessment and documentation. The community&lt;SPAN&gt;&amp;nbsp;cannot reliably provide this confirmation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;
&lt;P class="wnfdntd"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Mar 2026 10:31:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/cve-2023-51385-and-cve-2023-38408-in-runtime-17-3-lts-in-azure/m-p/151985#M53734</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-03-25T10:31:55Z</dc:date>
    </item>
  </channel>
</rss>

