<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vbs-Enclave on CuraSec</title><link>https://curasec.metacog.co.kr/tags/vbs-enclave/</link><description>Recent content in Vbs-Enclave on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 14 Oct 2026 15:48:57 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/vbs-enclave/index.xml" rel="self" type="application/rss+xml"/><item><title>Researchers Break Windows VBS Enclave via 4-Byte Write and Timing Bug</title><link>https://curasec.metacog.co.kr/insights/2026-10-14-four-byte-write-and-timing-bug-let-researchers-run-code-in-w/</link><pubDate>Wed, 14 Oct 2026 15:48:57 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-14-four-byte-write-and-timing-bug-let-researchers-run-code-in-w/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Novel lab research demonstrating code execution inside a Windows VBS enclave protecting SmartScreen credential data — no patch, no CVE, no exploitation signal yet, but worth understanding the attack surface if you rely on VBS enclaves for secrets isolation.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Pure research with no IOCs, no observed in-the-wild activity, and no detection surface described; file it as context for how VBS enclave isolation can fail, but no hunt or rule work is actionable today.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>