<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Privilege Escalation on Byte JMP</title>
    <link>https://bytejmp.com/tags/privilege-escalation/</link>
    <description>Recent content in Privilege Escalation on Byte JMP</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 25 May 2026 14:00:00 -0300</lastBuildDate><atom:link href="https://bytejmp.com/tags/privilege-escalation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Potato Family — Windows Privilege Escalation (2016–2024)</title>
      <link>https://bytejmp.com/posts/potato-privesc-windows/</link>
      <pubDate>Mon, 25 May 2026 14:00:00 -0300</pubDate>
      
      <guid>https://bytejmp.com/posts/potato-privesc-windows/</guid>
      
      <description>TL;DR Potato attacks exploit Windows service accounts that hold SeImpersonatePrivilege or SeAssignPrimaryTokenPrivilege. The core technique forces a privileged process (usually SYSTEM) to authenticate to an attacker-controlled server via NTLM, then impersonates the captured token to spawn a SYSTEM shell. Since 2016, over a dozen variants have emerged — each bypassing a specific Microsoft patch or restriction. This post maps the entire family: how each variant works, why the previous one stopped working, and when to use which.</description>
      
    </item>
    
  </channel>
</rss>
