<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Archive Security on Nalar</title>
    <link>https://nalar.dev/tags/archive-security/</link>
    <description>Recent content in Archive Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/archive-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure Archive Extraction Against Path Traversal</title>
      <link>https://nalar.dev/secure-archive-extraction-against-path-traversal/</link>
      <pubDate>Fri, 11 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/secure-archive-extraction-against-path-traversal/</guid>
      <description>&lt;p&gt;Archive extraction looks simple: open a ZIP or TAR file, iterate over its entries, and write each entry under a destination directory. The dangerous detail is that archive entries carry names and, in some formats, filesystem object types. Those fields come from the archive creator.&lt;/p&gt;&#xA;&lt;p&gt;If extraction code joins an untrusted entry name to a trusted destination without enforcing containment, an entry such as &lt;code&gt;../../app/config.json&lt;/code&gt; can escape the intended directory. A crafted archive can then overwrite files that the application account is permitted to modify.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
