<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vulnerability-Research on harpi - Security Researcher</title><link>https://harpi.cc/categories/vulnerability-research/</link><description>Recent content in Vulnerability-Research on harpi - Security Researcher</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 06 Apr 2026 16:17:15 +0300</lastBuildDate><atom:link href="https://harpi.cc/categories/vulnerability-research/index.xml" rel="self" type="application/rss+xml"/><item><title>Shaking the Mesh: Four Memory Corruption Bugs in VTK's GLTF Loader</title><link>https://harpi.cc/blog/cves/vtk-gltf/</link><pubDate>Thu, 30 Oct 2025 00:00:00 +0000</pubDate><guid>https://harpi.cc/blog/cves/vtk-gltf/</guid><description>&lt;blockquote>
&lt;p>&lt;em>&amp;ldquo;The future is already here — it&amp;rsquo;s just not evenly distributed.&amp;rdquo;&lt;/em> — William Gibson&lt;/p>&lt;/blockquote>
&lt;h2 id="how-i-got-here">How I Got Here&lt;/h2>
&lt;p>In mid-2025 I scoped out an engagement for &lt;a href="https://www.radicallyopensecurity.com/">Radically Open Security&lt;/a> targeting &lt;a href="https://f3d.app/">F3D&lt;/a> — a fast, minimalist 3D viewer that supports dozens of file formats — and its library counterpart, &lt;code>libf3d&lt;/code>. The proposal focused on three attack surfaces:&lt;/p>
&lt;blockquote>
&lt;p>Code audit and pentesting of &lt;code>f3d&lt;/code> and &lt;code>libf3d&lt;/code>.&lt;/p>
&lt;p>Our primary target is the &lt;code>libf3d&lt;/code> since its API is used by third-party projects and security issues are more critical.&lt;/p></description></item><item><title>The Binary Switcheroo: Turning a KDE File Manager Into a Local Privilege Escalation</title><link>https://harpi.cc/blog/cves/kde-kio-admin/</link><pubDate>Thu, 15 May 2025 00:00:00 +0000</pubDate><guid>https://harpi.cc/blog/cves/kde-kio-admin/</guid><description>&lt;blockquote>
&lt;p>&lt;em>&amp;ldquo;When you want to know how things really work, study them when they&amp;rsquo;re coming apart.&amp;rdquo;&lt;/em> — William Gibson&lt;/p>&lt;/blockquote>
&lt;h2 id="how-i-got-here">How I Got Here&lt;/h2>
&lt;p>In late 2024 I scoped out an engagement for &lt;a href="https://www.radicallyopensecurity.com/">Radically Open Security&lt;/a> targeting &lt;code>kio-admin&lt;/code> — the KDE component that gives Dolphin (KDE&amp;rsquo;s file manager) the ability to perform file operations as root. The proposal was straightforward:&lt;/p>
&lt;blockquote>
&lt;p>Code audit and pentesting of &lt;code>Dolphin&lt;/code> authorisation mechanisms as they are provided by &lt;code>kio-admin&lt;/code> and &lt;code>kio&lt;/code> framework.&lt;/p></description></item><item><title>Django Allauth: Account Takeover via Provider Identifier Mutability</title><link>https://harpi.cc/blog/cves/django-allauth/django-allauth-account-takeover/</link><pubDate>Wed, 25 Dec 2024 00:00:00 +0000</pubDate><guid>https://harpi.cc/blog/cves/django-allauth/django-allauth-account-takeover/</guid><description>&lt;blockquote>
&lt;p>&lt;em>&amp;ldquo;There&amp;rsquo;s always a side door.&amp;rdquo;&lt;/em>&lt;/p>&lt;/blockquote>
&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>I discovered an account takeover vulnerability in &lt;a href="https://github.com/pennersr/django-allauth">django-allauth&lt;/a>, one of the most widely-used authentication libraries for Django. The vulnerability allows an attacker to impersonate arbitrary users by exploiting how certain OAuth providers&amp;rsquo; identifiers are resolved.&lt;/p>
&lt;h2 id="vulnerability-details">Vulnerability Details&lt;/h2>
&lt;p>&lt;strong>CVE:&lt;/strong> CVE-2025-65431
&lt;strong>Type:&lt;/strong> Improper Authentication / Account Takeover (CWE-287)
&lt;strong>Impact:&lt;/strong> Account Impersonation
&lt;strong>Affected Versions:&lt;/strong> django-allauth &amp;lt; 65.13.0&lt;/p>
&lt;h3 id="the-bug">The Bug&lt;/h3>
&lt;p>Both the Okta and NetIQ providers were using &lt;code>preferred_username&lt;/code> as the identifier for third-party provider accounts. This value is &lt;strong>mutable&lt;/strong> — users can change their &lt;code>preferred_username&lt;/code> on the identity provider side.&lt;/p></description></item></channel></rss>