<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://themcsam.github.io/</id><title>McSam's blog</title><subtitle>A friendly blog platform where i'll discuss about my findings, tricks and techniques used in compromising targets. Have fun reading i hope you learn something new.</subtitle> <updated>2026-02-09T22:58:35+00:00</updated> <author> <name>McSam</name> <uri>https://themcsam.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://themcsam.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://themcsam.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 McSam </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Authenticated RCE and File Read Vulnerabilities Found in CyberPanel</title><link href="https://themcsam.github.io/posts/cyberpanel-vulnerabilties/" rel="alternate" type="text/html" title="Authenticated RCE and File Read Vulnerabilities Found in CyberPanel" /><published>2026-01-17T18:45:00+00:00</published> <updated>2026-01-20T21:39:54+00:00</updated> <id>https://themcsam.github.io/posts/cyberpanel-vulnerabilties/</id> <content type="text/html" src="https://themcsam.github.io/posts/cyberpanel-vulnerabilties/" /> <author> <name>McSam</name> </author> <category term="Vulnerability Research" /> <category term="Bug Hunting" /> <summary>Technical breakdown of vulnerabilties i discovered in CyberPanel Introduction During the Christmas break, my friend @whiteov3rflow and I decided to undertake a small research project exploring the security posture of cloud hosting panels. We selected CyberPanel as our starting point and spent the holidays examining its features, behavior, and underlying code paths. The research turned out to...</summary> </entry> <entry><title>Interpreter @ SNHT CTF '25</title><link href="https://themcsam.github.io/posts/interpreter/" rel="alternate" type="text/html" title="Interpreter @ SNHT CTF &amp;apos;25" /><published>2025-10-30T20:45:00+00:00</published> <updated>2025-12-30T18:49:52+00:00</updated> <id>https://themcsam.github.io/posts/interpreter/</id> <content type="text/html" src="https://themcsam.github.io/posts/interpreter/" /> <author> <name>McSam</name> </author> <category term="CTF" /> <category term="SNHT CTF '25" /> <summary>Interpreter - SNHT CTF ‘25 Difficulty: Easy Overview: Interpreter is a challenge created by a friend of mine, 0x1337 (aka blood pwn). If you are into pwn, you have probably come across his work. His blog is packed with really solid writeups, which you can check out here. The challenge starts off with a buffer overflow vulnerability. We take advantage of this to leak libc addresses, and from t...</summary> </entry> <entry><title>Reader @ Flagyard</title><link href="https://themcsam.github.io/posts/reader/" rel="alternate" type="text/html" title="Reader @ Flagyard" /><published>2025-10-30T20:45:00+00:00</published> <updated>2025-10-30T20:45:00+00:00</updated> <id>https://themcsam.github.io/posts/reader/</id> <content type="text/html" src="https://themcsam.github.io/posts/reader/" /> <author> <name>McSam</name> </author> <category term="CTF" /> <category term="Flagyard" /> <summary>Reader - Flagyard Difficulty: Easy Overview: The Reader challenge threads two complementary vulnerabilities into a compact exploit chain. On the one hand, the service exposes an arbitrary file-read primitive that lets us exfiltrate runtime memory. On the other hand, a classic stack buffer overflow (no stack canary) gives us a write primitive powerful enough to overwrite saved frame data and th...</summary> </entry> <entry><title>Lucky @ Flagyard</title><link href="https://themcsam.github.io/posts/lucky/" rel="alternate" type="text/html" title="Lucky @ Flagyard" /><published>2025-10-03T20:45:00+00:00</published> <updated>2025-10-31T10:21:26+00:00</updated> <id>https://themcsam.github.io/posts/lucky/</id> <content type="text/html" src="https://themcsam.github.io/posts/lucky/" /> <author> <name>McSam</name> </author> <category term="CTF" /> <category term="Flagyard" /> <summary>Lucky - Flagyard Difficulty: Easy Overview: Lucky chains a stack-reuse bug to force a local variable to attacker-controlled values, allowing bypass of safety checks. That bypass triggers an out-of-bounds write which lets you corrupt critical memory. A separate libc leak reveals a libc address so you can compute the base and turn the OOB write into full code execution. Basic File Checks First ...</summary> </entry> <entry><title>CVE-2024-39930 PoC - gogs ssh in-built server RCE</title><link href="https://themcsam.github.io/posts/gogs-RCE-PoC/" rel="alternate" type="text/html" title="CVE-2024-39930 PoC - gogs ssh in-built server RCE" /><published>2025-06-29T00:05:00+00:00</published> <updated>2025-07-01T16:16:11+00:00</updated> <id>https://themcsam.github.io/posts/gogs-RCE-PoC/</id> <content type="text/html" src="https://themcsam.github.io/posts/gogs-RCE-PoC/" /> <author> <name>McSam</name> </author> <category term="Vulnerability Research" /> <category term="Exploit Development" /> <summary>Vulnerability anaylsis and PoC Development for CVE-2024-39930 Introduction Gogs is a lightweight and self-hosted Git service that’s simple to set up and ideal for organizations that prefer to keep their source code off third-party platforms like GitHub. While Gogs offers many of the same features as GitHub, its self-hosted nature makes it particularly attractive for internal development enviro...</summary> </entry> </feed>
