<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dinesh Kumar</title>
    <description>The latest articles on DEV Community by Dinesh Kumar (@dinesh_kumar_6406).</description>
    <link>https://dev.to/dinesh_kumar_6406</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4145812%2Fca9901db-6785-49d7-a846-32ca5858e402.png</url>
      <title>DEV Community: Dinesh Kumar</title>
      <link>https://dev.to/dinesh_kumar_6406</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dinesh_kumar_6406"/>
    <language>en</language>
    <item>
      <title>DDRop: The $159 Attack That Breaks "Unbreakable" Cloud Encryption</title>
      <dc:creator>Dinesh Kumar</dc:creator>
      <pubDate>Sun, 27 Sep 2026 18:02:08 +0000</pubDate>
      <link>https://dev.to/dinesh_kumar_6406/ddrop-the-159-attack-that-breaks-unbreakable-cloud-encryption-5fad</link>
      <guid>https://dev.to/dinesh_kumar_6406/ddrop-the-159-attack-that-breaks-unbreakable-cloud-encryption-5fad</guid>
      <description>&lt;p&gt;If you've ever trusted "confidential computing" to keep your data safe from a cloud provider itself — even a malicious one — a paper disclosed this month should get your attention.&lt;/p&gt;

&lt;p&gt;Confidential computing (Intel TDX, AMD SEV-SNP) promises that even a malicious cloud provider with physical server access can't read your data — memory stays encrypted while it's actively in use. A paper disclosed this month, by researchers from KU Leuven, ETH Zurich, Durham University, and Google, shows that promise has a hole.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The core gap:&lt;/strong&gt; these systems verify that memory is encrypted correctly — but never verify it holds the most recent value. Confidential computing keeps a server's memory encrypted, so that even someone with physical access to the machine sees only scrambled data. To cover the large amount of memory that a cloud server uses, though, these designs omit a guarantee called freshness.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The attack, DDRop&lt;/strong&gt;: researchers built a $159 circuit board (an "interposer") that sits between the CPU and DDR5 memory and silently drops write commands. When the interposer drops a write, the earlier value stays in memory, and the processor reads it back as though the update had happened. The encryption engine detects nothing wrong.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; this isn't just data leakage. Researchers demonstrated that DDRop can achieve full control of protected virtual machines on Intel TDX by manipulating page table writes, enabling unauthorized memory access and attestation forgery — meaning a VM could falsely prove it's running untampered code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The catch:&lt;/strong&gt;it requires an attacker who already has software control of the server and brief physical access to install the hardware. Intel and AMD acknowledged the disclosure but noted physical-access attacks fall outside their threat model — a fair point, but a bit hollow if you chose confidential computing specifically to defend against a malicious insider with server access.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The uncomfortable part:&lt;/strong&gt; a simple software patch is not feasible due to the hardware-level vulnerability. This is architectural, not a Tuesday patch.&lt;/p&gt;

&lt;p&gt;Sources: The Hacker News, SC World&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>cloud</category>
      <category>mojo</category>
    </item>
  </channel>
</rss>
