<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>LARP research team</title><description>LARP is a team of vulnerability researchers and bug hunters. We find security bugs in software people rely on, report them to the vendor, and publish the details once they are fixed.</description><link>https://larp-security.com/</link><language>en</language><item><title>A two-byte heap overflow in a font shaping engine</title><link>https://larp-security.com/research/LARP-2026-014/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2026-014/</guid><description>The engine sizes a buffer from one field in the font and copies data based on another. A crafted font makes them disagree, which gives a two-byte heap overflow. We used it to corrupt a function pointer.</description><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate><category>memory</category><author>hello@larp.example (kaze &amp; m0th)</author></item><item><title>SSRF through PDF rendering in a document preview service</title><link>https://larp-security.com/research/LARP-2026-012/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2026-012/</guid><description>The service rendered uploaded PDFs on the server, and PDFs can load remote resources. That was enough to reach internal endpoints, including the cloud metadata service.</description><pubDate>Wed, 02 Sep 2026 00:00:00 GMT</pubDate><category>web</category><author>hello@larp.example (yuzu)</author></item><item><title>Intent redirection in an Android banking app</title><link>https://larp-security.com/research/LARP-2026-011/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2026-011/</guid><description>An exported activity forwarded any intent it received, which gave other apps access to components that were supposed to be private. We cover the bug, the fix, and a lint rule that catches it.</description><pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate><category>mobile</category><author>hello@larp.example (sable)</author></item><item><title>Recovering an IoT pairing key from two packets</title><link>https://larp-security.com/research/LARP-2026-010/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2026-010/</guid><description>The pairing counter resets on every reboot, so the same nonce gets used twice. With two captured handshakes, the session key can be recovered.</description><pubDate>Fri, 05 Jun 2026 00:00:00 GMT</pubDate><category>crypto</category><author>hello@larp.example (m0th &amp; ampere)</author></item><item><title>Use-after-free in a Linux filesystem rename path</title><link>https://larp-security.com/research/LARP-2025-031/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2025-031/</guid><description>A race between two rename calls drops a reference one time too many. We explain the race and how we made the exploit reliable on stock hardware.</description><pubDate>Thu, 11 Dec 2025 00:00:00 GMT</pubDate><category>kernel</category><author>hello@larp.example (kaze)</author></item><item><title>Bypassing secure boot with a $40 voltage glitcher</title><link>https://larp-security.com/research/LARP-2025-027/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2025-027/</guid><description>A glitch at the right moment skips the signature check in the boot ROM. Most of the work was finding the timing. The bug is in ROM, so it cannot be patched.</description><pubDate>Thu, 09 Oct 2025 00:00:00 GMT</pubDate><category>hardware</category><author>hello@larp.example (ampere)</author></item><item><title>From prototype pollution to RCE in a Node.js template engine</title><link>https://larp-security.com/research/LARP-2025-019/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2025-019/</guid><description>Getting to code execution took eleven attempts. We wrote up the failed ones as well, since they show where the engine is actually hardened.</description><pubDate>Sun, 22 Jun 2025 00:00:00 GMT</pubDate><category>web</category><author>hello@larp.example (yuzu &amp; sable)</author></item><item><title>Type confusion in a JavaScript JIT, for beginners</title><link>https://larp-security.com/research/LARP-2025-008/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2025-008/</guid><description>A step by step walkthrough, from how the JIT works to a working read/write primitive. Everything in it can be reproduced on a laptop.</description><pubDate>Fri, 14 Mar 2025 00:00:00 GMT</pubDate><category>memory</category><author>hello@larp.example (m0th)</author></item><item><title>Releasing our file parser fuzzer</title><link>https://larp-security.com/research/LARP-2024-022/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2024-022/</guid><description>The harness generator we use internally, cleaned up and released under the MIT license.</description><pubDate>Sat, 30 Nov 2024 00:00:00 GMT</pubDate><category>tooling</category><author>hello@larp.example (the whole team)</author></item><item><title>Our first year: 31 bugs, 4 lessons, 1 apology</title><link>https://larp-security.com/research/LARP-2024-007/</link><guid isPermaLink="true">https://larp-security.com/research/LARP-2024-007/</guid><description>What went well, what didn&apos;t, and a disclosure we handled badly.</description><pubDate>Tue, 02 Apr 2024 00:00:00 GMT</pubDate><category>notes</category><author>hello@larp.example (the whole team)</author></item></channel></rss>