<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Appsec on phinguin123</title>
    <link>http://phinguin.dev/tags/appsec/</link>
    <description>Recent content in Appsec on phinguin123</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 phinguin</copyright>
    <lastBuildDate>Wed, 01 Jul 2026 20:01:00 +0900</lastBuildDate>
    <atom:link href="http://phinguin.dev/tags/appsec/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pen-Testing My Own Upload Endpoint</title>
      <link>http://phinguin.dev/blog/accidentally-safe-isnt-safe/</link>
      <pubDate>Wed, 01 Jul 2026 20:01:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/accidentally-safe-isnt-safe/</guid>
      <description>Tried to path-traverse my own homework upload API. It held up, but only because of a timestamp prefix I never meant as a security thing.</description>
    </item>
    <item>
      <title>I Pulled /etc/passwd Off My Own Server</title>
      <link>http://phinguin.dev/blog/reading-my-own-etc-passwd/</link>
      <pubDate>Mon, 29 Jun 2026 20:48:00 +0900</pubDate>
      <guid>http://phinguin.dev/blog/reading-my-own-etc-passwd/</guid>
      <description>An nginx 400 felt like a fix. send_from_directory felt like a fix. Then a different endpoint handed me /etc/passwd, and the real question was how bad that actually is.</description>
    </item>
  </channel>
</rss>
