<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exhibitor Unauthenticated RCE on Chief Dennis' Blog</title><link>https://chiefdennis.github.io/tags/exhibitor-unauthenticated-rce/</link><description>Recent content in Exhibitor Unauthenticated RCE on Chief Dennis' Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 29 Nov 2025 11:00:00 +0100</lastBuildDate><atom:link href="https://chiefdennis.github.io/tags/exhibitor-unauthenticated-rce/index.xml" rel="self" type="application/rss+xml"/><item><title>Pelican Offsec Walkthrough</title><link>https://chiefdennis.github.io/posts/pelican-walkthrough/</link><pubDate>Sat, 29 Nov 2025 11:00:00 +0100</pubDate><guid>https://chiefdennis.github.io/posts/pelican-walkthrough/</guid><description>&lt;h2 id="pelican-offsec-walkthrough">
 Pelican OffSec Walkthrough
 &lt;a class="heading-link" href="#pelican-offsec-walkthrough">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h2>
&lt;p>&lt;img src="https://chiefdennis.github.io/posts/pelican-walkthrough/Picture_0.png" alt="image">&lt;/p>
&lt;p>This walkthrough covers the full exploitation path for the Pelican target, from initial reconnaissance to root compromise and post-exploitation considerations. We focus on service enumeration, misconfigurations, abusing an exposed Exhibitor instance, credential extraction through memory dumping, and privilege escalation.&lt;/p>
&lt;h3 id="1-reconnaissance">
 1. Reconnaissance
 &lt;a class="heading-link" href="#1-reconnaissance">
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading">&lt;/i>
 &lt;span class="sr-only">Link to heading&lt;/span>
 &lt;/a>
&lt;/h3>
&lt;p>First, a ping is made to verify connection with the machine:&lt;/p></description></item></channel></rss>