<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secure-Design on CuraSec</title><link>https://curasec.metacog.co.kr/tags/secure-design/</link><description>Recent content in Secure-Design on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Aug 2026 13:39:41 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/secure-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Canonicalization Failures Systematized Across Cryptographic Ecosystems</title><link>https://curasec.metacog.co.kr/insights/2026-08-10-canonicalization-failures-as-a-recurring-vulnerability-class/</link><pubDate>Mon, 10 Aug 2026 13:39:41 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-10-canonicalization-failures-as-a-recurring-vulnerability-class/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> This paper provides a cross-ecosystem taxonomy of canonicalization failures (transaction malleability, hash-chain malleability, etc.) and a practical review procedure for identifying this class of defect in cryptographic code. Worth reading before designing or auditing any system where a hash, signature, or replay-protection scheme depends on serialized representations.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>