<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Embedded-Systems on CuraSec</title><link>https://curasec.metacog.co.kr/tags/embedded-systems/</link><description>Recent content in Embedded-Systems on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 11:49:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/embedded-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Six U-Boot Flaws Enable Crash or Pre-Boot Code Execution</title><link>https://curasec.metacog.co.kr/insights/2026-07-11-six-new-u-boot-flaws-could-let-malicious-images-crash-device/</link><pubDate>Sat, 11 Jul 2026 11:49:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-11-six-new-u-boot-flaws-could-let-malicious-images-crash-device/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Two of the six flaws allow pre-OS code execution if an attacker can supply a malicious boot image — relevant to anyone managing routers, smart cameras, or servers with BMC/management chips running U-Boot. No KEV or PoC yet, so plan to inventory U-Boot-dependent devices and track vendor firmware patches as they release.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, no active exploitation, and boot-level compromise is largely invisible to SIEM/EDR — nothing to hunt or detect today, but understanding pre-boot attack surfaces informs triage if a device integrity alert surfaces later.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>