<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Tagging on SILO</title>
    <link>https://silo.pgsty.com/tags/tagging/</link>
    <description>Recent content in Tagging on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Thu, 12 Nov 2026 03:50:08 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/tagging/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>SN-2026-024: GetObjectAttributes and Read-Only ZIP Archive Tag-Policy and GetObject Bypass</title>
        <link>https://silo.pgsty.com/blog/security/20261111-attributes-and-archive-tag-authz/</link>
        <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/security/20261111-attributes-and-archive-tag-authz/</guid>
        <description>&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Fixed on &lt;code&gt;main&lt;/code&gt; (&lt;a href=&#34;https://github.com/pgsty/silo/commit/f746d07076faaf9be1479aadfaf904a4793fa8c0&#34;&gt;&lt;code&gt;f746d0707&lt;/code&gt;&lt;/a&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/commit/296c9710b16467e53fd4d861bf0b01f35fe6e555&#34;&gt;&lt;code&gt;296c9710b&lt;/code&gt;&lt;/a&gt;); scheduled for the next post-&lt;a href=&#34;https://silo.pgsty.com/blog/release/silo-20261109/&#34;&gt;&lt;code&gt;20261109&lt;/code&gt;&lt;/a&gt; Server release&lt;br&gt;&#xA;&lt;strong&gt;Identifier:&lt;/strong&gt; &lt;code&gt;SN-2026-024&lt;/code&gt; (&lt;a href=&#34;https://silo.pgsty.com/about/security-advisories/#sn-2026-024&#34;&gt;Security Advisory Ledger&lt;/a&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/issues/342&#34;&gt;#342&lt;/a&gt;)&lt;br&gt;&#xA;&lt;strong&gt;Severity:&lt;/strong&gt; High&lt;br&gt;&#xA;&lt;strong&gt;Affected scope:&lt;/strong&gt; &lt;strong&gt;SILO Server&lt;/strong&gt; (&lt;code&gt;RELEASE.2026-11-09T00-00-00Z&lt;/code&gt; and earlier) and inherited upstream MinIO releases since &lt;code&gt;2021-06-10&lt;/code&gt; (&lt;a href=&#34;https://github.com/pgsty/silo/commit/ba5fb2365cc9797fcf4952041e9cfb035b8277f8&#34;&gt;&lt;code&gt;ba5fb2365&lt;/code&gt;&lt;/a&gt;) and &lt;code&gt;2024-01-05&lt;/code&gt; (&lt;a href=&#34;https://github.com/pgsty/silo/commit/9b8ba97f9fc0a39ea6632443a102bd42f8067da3&#34;&gt;&lt;code&gt;9b8ba97f9&lt;/code&gt;&lt;/a&gt;)&lt;br&gt;&#xA;&lt;strong&gt;Unaffected components:&lt;/strong&gt; &lt;code&gt;silo-console&lt;/code&gt;, &lt;code&gt;mcli&lt;/code&gt;, &lt;code&gt;silo-pkg&lt;/code&gt;, and &lt;code&gt;kes&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Standard &lt;code&gt;GetObject&lt;/code&gt; and &lt;code&gt;HeadObject&lt;/code&gt; handlers in SILO authenticate the caller first, read the addressed object version&amp;rsquo;s &lt;code&gt;ObjectInfo&lt;/code&gt;, and then authorize &lt;code&gt;s3:GetObject&lt;/code&gt; (or &lt;code&gt;s3:GetObjectVersion&lt;/code&gt;) against &lt;code&gt;objInfo.UserTags&lt;/code&gt; so IAM policies conditioned on &lt;code&gt;s3:ExistingObjectTag/&amp;lt;key&amp;gt;&lt;/code&gt; take effect. Inherited from upstream MinIO, two read surfaces bypassed that post-metadata authorization step: &lt;code&gt;GetObjectAttributes&lt;/code&gt; (&lt;code&gt;GET /&amp;lt;bucket&amp;gt;/&amp;lt;key&amp;gt;?attributes&lt;/code&gt;) and the read-only &lt;code&gt;.zip&lt;/code&gt; archive S3 extension (&lt;code&gt;x-minio-extract: true&lt;/code&gt; on &lt;code&gt;GET&lt;/code&gt;, &lt;code&gt;HEAD&lt;/code&gt;, and &lt;code&gt;ListObjectsV2&lt;/code&gt;). In addition, &lt;code&gt;ListObjectsV2&lt;/code&gt; archive member listing enumerated &lt;code&gt;.zip&lt;/code&gt; contents using only bucket-level &lt;code&gt;s3:ListBucket&lt;/code&gt; without checking &lt;code&gt;s3:GetObject&lt;/code&gt; on the archive object itself, and reading an unindexed &lt;code&gt;.zip&lt;/code&gt; archive persisted generated index metadata back onto the object during read verbs.&lt;/p&gt;</description>
      </item>
    <item>
        <title>SN-2026-022: Active-Active Tagging Proxy Authentication and Remote Tag-Policy Bypass</title>
        <link>https://silo.pgsty.com/blog/security/20261111-tagging-replication-proxy-auth/</link>
        <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/security/20261111-tagging-replication-proxy-auth/</guid>
        <description>&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Fixed on &lt;code&gt;main&lt;/code&gt; (&lt;a href=&#34;https://github.com/pgsty/silo/commit/14ecb222e714eaa69e712b7497e500d72854f697&#34;&gt;&lt;code&gt;14ecb222e&lt;/code&gt;&lt;/a&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/commit/67a90dfef458d3e5228e849711118bc162abed30&#34;&gt;&lt;code&gt;67a90dfef&lt;/code&gt;&lt;/a&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/commit/293ab78b4cc505c3ab8170a4b2b4b29c04ad74f9&#34;&gt;&lt;code&gt;293ab78b4&lt;/code&gt;&lt;/a&gt;); scheduled for the next post-&lt;a href=&#34;https://silo.pgsty.com/blog/release/silo-20261109/&#34;&gt;&lt;code&gt;20261109&lt;/code&gt;&lt;/a&gt; Server release&lt;br&gt;&#xA;&lt;strong&gt;Identifier:&lt;/strong&gt; &lt;code&gt;SN-2026-022&lt;/code&gt; (&lt;a href=&#34;https://silo.pgsty.com/about/security-advisories/#sn-2026-022&#34;&gt;Security Advisory Ledger&lt;/a&gt;, &lt;a href=&#34;https://github.com/pgsty/silo/issues/337&#34;&gt;#337&lt;/a&gt;)&lt;br&gt;&#xA;&lt;strong&gt;Severity:&lt;/strong&gt; Critical&lt;br&gt;&#xA;&lt;strong&gt;Affected scope:&lt;/strong&gt; &lt;strong&gt;SILO Server&lt;/strong&gt; (&lt;code&gt;RELEASE.2026-11-09T00-00-00Z&lt;/code&gt; and earlier) and inherited upstream MinIO releases since &lt;code&gt;2024-01-12&lt;/code&gt; (&lt;a href=&#34;https://github.com/pgsty/silo/commit/b2b26d9c958a82fbd9f7e0dc70fc2133838576d0&#34;&gt;&lt;code&gt;b2b26d9c9&lt;/code&gt;&lt;/a&gt;)&lt;br&gt;&#xA;&lt;strong&gt;Unaffected components:&lt;/strong&gt; &lt;code&gt;silo-console&lt;/code&gt;, &lt;code&gt;mcli&lt;/code&gt;, &lt;code&gt;silo-pkg&lt;/code&gt;, and &lt;code&gt;kes&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;When active-active bucket or site replication is enabled, an S3 object version may temporarily or permanently reside on a remote replication target while absent from the local cluster receiving a client request. To keep tagging operations transparent across peers, &lt;code&gt;GetObjectTaggingHandler&lt;/code&gt;, &lt;code&gt;PutObjectTaggingHandler&lt;/code&gt;, and &lt;code&gt;DeleteObjectTaggingHandler&lt;/code&gt; (&lt;code&gt;cmd/object-handlers.go&lt;/code&gt;) proxy requests for locally missing objects to active-active replication targets via &lt;code&gt;proxyTaggingToRepTarget&lt;/code&gt; (&lt;code&gt;cmd/bucket-replication.go&lt;/code&gt;), signing the outbound request with the server&amp;rsquo;s privileged replication credentials.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
