<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: DeepSeek incident updates</title>
  <link>https://pwn.watch/t/deepseek</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Wed, 29 Jan 2025 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/t/deepseek/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[high] DeepSeek leaves ClickHouse database open: chat logs and API keys exposed</title>
    <link>https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/deepseek-exposed-clickhouse-database-january-2025</guid>
    <pubDate>Wed, 29 Jan 2025 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;Wiz found two DeepSeek ClickHouse instances open to the internet without authentication. Its query interface allowed arbitrary SQL and exposed a log_stream table with over a million entries, including plaintext chat history, API keys and backend details. DeepSeek locked it down within an hour of being told.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; Database secured by DeepSeek&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-01-29: Wiz finds the exposed database and reports it; DeepSeek secures it within an hour (&lt;a href=&quot;https://www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
</channel>
</rss>
