<?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 Re: Have a pi(e) and eat it in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/21028#M2561</link>
    <description>&lt;P&gt;Why not? If I send you a cool app and you run it granting me access to your network, I poke around the network and see Linux running on a Pi, if I can pivot to that then I would try all the privesc methods at my disposal. Now your Pi is being used as a C2 server or whatever else the threat actor wants &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 09 Apr 2019 20:58:17 GMT</pubDate>
    <dc:creator>OS22783</dc:creator>
    <dc:date>2019-04-09T20:58:17Z</dc:date>
    <item>
      <title>Have a pi(e) and eat it</title>
      <link>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/20997#M2554</link>
      <description>&lt;P&gt;Seriously, someone wants to attack my Raspberry Pi ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2018-18068" target="_blank"&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-18068&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 14:39:55 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/20997#M2554</guid>
      <dc:creator>Chuxing</dc:creator>
      <dc:date>2019-04-09T14:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: Have a pi(e) and eat it</title>
      <link>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/21012#M2559</link>
      <description>&lt;P&gt;Future 'con presentations have to come from somewhere, even if they present no real world threat. In this case I suspect this is probably what is going on here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Somehow I skipped over this information when skimming my daily CVE browsing the past few days.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Food for thought.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- b/eads&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 18:01:34 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/21012#M2559</guid>
      <dc:creator>Beads</dc:creator>
      <dc:date>2019-04-09T18:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: Have a pi(e) and eat it</title>
      <link>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/21028#M2561</link>
      <description>&lt;P&gt;Why not? If I send you a cool app and you run it granting me access to your network, I poke around the network and see Linux running on a Pi, if I can pivot to that then I would try all the privesc methods at my disposal. Now your Pi is being used as a C2 server or whatever else the threat actor wants &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 20:58:17 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Have-a-pi-e-and-eat-it/m-p/21028#M2561</guid>
      <dc:creator>OS22783</dc:creator>
      <dc:date>2019-04-09T20:58:17Z</dc:date>
    </item>
  </channel>
</rss>

