<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Regarding impoper tagging of node-tar vulnerability with alpine-tar package when using prisma scan tool in Cortex Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-cloud-discussions/regarding-impoper-tagging-of-node-tar-vulnerability-with-alpine/m-p/1248768#M1553</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Below are docker file instruction&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;FROM docker.io/library/alpine:latest&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;RUN apk update &amp;amp;&amp;amp; apk add --no-cache tar&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With this only tar package is being installed within image. But during scan of same image with Prisma security scan tool, it is incorrectly mapping same with "&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2018-20834&amp;quot;" target="_blank"&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-20834"&lt;/A&gt;&amp;nbsp;having node-tar vulnerability. Also proving fix like below that is again irrelavant.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE style="border-collapse: collapse; width: 65pt;" border="0" width="87" cellspacing="0" cellpadding="0"&gt;&lt;COLGROUP&gt;&lt;COL style="width: 65pt;" width="87" /&gt; &lt;/COLGROUP&gt;
&lt;TBODY&gt;
&lt;TR style="height: 16.0pt;"&gt;
&lt;TD width="87" height="21" style="height: 16.0pt; width: 65pt;"&gt;&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2018-20834" target="_blank"&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-20834&lt;/A&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
    <pubDate>Mon, 23 Feb 2026 08:59:42 GMT</pubDate>
    <dc:creator>gauravj139</dc:creator>
    <dc:date>2026-02-23T08:59:42Z</dc:date>
    <item>
      <title>Regarding impoper tagging of node-tar vulnerability with alpine-tar package when using prisma scan tool</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-cloud-discussions/regarding-impoper-tagging-of-node-tar-vulnerability-with-alpine/m-p/1248768#M1553</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Below are docker file instruction&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;FROM docker.io/library/alpine:latest&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;RUN apk update &amp;amp;&amp;amp; apk add --no-cache tar&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;With this only tar package is being installed within image. But during scan of same image with Prisma security scan tool, it is incorrectly mapping same with "&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2018-20834&amp;quot;" target="_blank"&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-20834"&lt;/A&gt;&amp;nbsp;having node-tar vulnerability. Also proving fix like below that is again irrelavant.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE style="border-collapse: collapse; width: 65pt;" border="0" width="87" cellspacing="0" cellpadding="0"&gt;&lt;COLGROUP&gt;&lt;COL style="width: 65pt;" width="87" /&gt; &lt;/COLGROUP&gt;
&lt;TBODY&gt;
&lt;TR style="height: 16.0pt;"&gt;
&lt;TD width="87" height="21" style="height: 16.0pt; width: 65pt;"&gt;&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2018-20834" target="_blank"&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-20834&lt;/A&gt;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Mon, 23 Feb 2026 08:59:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-cloud-discussions/regarding-impoper-tagging-of-node-tar-vulnerability-with-alpine/m-p/1248768#M1553</guid>
      <dc:creator>gauravj139</dc:creator>
      <dc:date>2026-02-23T08:59:42Z</dc:date>
    </item>
  </channel>
</rss>

