<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Archive Extraction on Nalar</title>
    <link>https://nalar.dev/tags/archive-extraction/</link>
    <description>Recent content in Archive Extraction on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/archive-extraction/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keep Archive Extraction Inside Its Destination</title>
      <link>https://nalar.dev/keep-archive-extraction-inside-its-destination/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/keep-archive-extraction-inside-its-destination/</guid>
      <description>&lt;p&gt;Extracting an archive looks like a file-copying task: read each entry, join its name to a destination directory, and write the bytes. The security problem is that an archive entry name is input chosen by whoever created the archive. If that name can influence the output path without a containment check, extraction can write outside the directory the application intended to grant.&lt;/p&gt;&#xA;&lt;p&gt;The consequence is broader than a misplaced file. Depending on the process&amp;rsquo;s permissions, an escaped write may replace application data, configuration, generated assets, or another file that the extractor can modify.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
