<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AVIF on Matt Suiche</title><link>https://www.msuiche.com/tags/avif/</link><description>Recent content in AVIF on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://www.msuiche.com/tags/avif/index.xml" rel="self" type="application/rss+xml"/><item><title>Four libheif Defects You Can Catch Before Decoding</title><link>https://www.msuiche.com/posts/four-libheif-defects-you-can-catch-before-decoding/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/four-libheif-defects-you-can-catch-before-decoding/</guid><description>&lt;p&gt;Hacktron&amp;rsquo;s &lt;a href="https://heif-heist.com/" target="_blank" rel="noopener"&gt;HEIF Heist&lt;/a&gt; research turned libheif into the most interesting image-parsing target of the year. Their team, led by &lt;a href="https://x.com/rootxharsh" target="_blank" rel="noopener"&gt;Harsh Jaiswal&lt;/a&gt; with &lt;a href="https://x.com/S1r1u5_" target="_blank" rel="noopener"&gt;Mohan SRK&lt;/a&gt;, Rahul Maini and Sudhanshu Rajbhar, chained decoder bugs into remote code execution against OpenAI, Slack, Meta, GitHub Enterprise, Discourse and Next.js, all through ordinary image uploads and image optimization endpoints.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://www.hacktron.ai/blog/hacking-openai" target="_blank" rel="noopener"&gt;OpenAI chain&lt;/a&gt; reads like a tour of how deep an image decoder sits in a modern stack: a HEIC file uploaded to community.openai.com, converted by ImageMagick, parsed by libheif 1.19.7, heap overflow, remote code execution, administrative access to the forum, then an SSO flaw that gave them an OpenAI employee account with Codex access to GitHub and, through it, the internal monorepo. OpenAI paid $6,500. The libheif bug they used carried no CVE at the time, because upstream had fixed it quietly.&lt;/p&gt;</description></item></channel></rss>