<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>url on Security, Tech, And Ramblings</title>
    <link>/tags/url/</link>
    <description>Recent content in url on Security, Tech, And Ramblings</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright © {year} Sean Marpo. All Rights Reserved.</copyright>
    <lastBuildDate>Sat, 12 Feb 2022 12:09:08 -0800</lastBuildDate><atom:link href="/tags/url/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Path Traversal and SSRF</title>
      <link>/posts/path-traversal-and-ssrf/</link>
      <pubDate>Sat, 12 Feb 2022 12:09:08 -0800</pubDate>
      
      <guid>/posts/path-traversal-and-ssrf/</guid>
      <description>I was recently working on a security review, and I came across an anti-pattern I&amp;rsquo;ve seen time and time again. Sure, it might be obvious, but this was a relatively tenured developer who suggested this particular solution. It&amp;rsquo;s seemingly pervasive enough that it warrants digging into. So, with that in mind, let&amp;rsquo;s chat about path traversal and SSRF.
The Context I was performing an app/code review of a new &amp;ldquo;thing&amp;rdquo; to keep this vague enough.</description>
    </item>
    
  </channel>
</rss>
