<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ppid on kanyo's blog</title><link>https://chaelsoo.me/tags/ppid/</link><description>Recent content in Ppid on kanyo's blog</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chaelsoo.me/tags/ppid/index.xml" rel="self" type="application/rss+xml"/><item><title>HTB: Pov</title><link>https://chaelsoo.me/writeups/htb-pov/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://chaelsoo.me/writeups/htb-pov/</guid><description>&lt;p&gt;Windows box, only port 80. The main site drops a subdomain in the contact section, and that subdomain has a portfolio with a CV download feature that doesn&amp;rsquo;t sanitize the file path. Reading &lt;code&gt;web.config&lt;/code&gt; through that LFI leaks the ASP.NET machineKey. From there the attack is elegant: the machineKey signs and encrypts ViewState, so with it you can forge a malicious ViewState that the server deserializes as trusted, and deserialization in .NET gives you code execution. The second half is about SeDebugPrivilege and parent PID spoofing, a technique that lets you inherit a SYSTEM token without touching lsass.&lt;/p&gt;</description></item></channel></rss>