<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Restricted Shell on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/restricted-shell/</link>
    <description>Recent content in Restricted Shell on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jul 2019 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/restricted-shell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to break out of restricted shells with tcpdump</title>
      <link>https://insinuator.net/2019/07/how-to-break-out-of-restricted-shells-with-tcpdump/</link>
      <pubDate>Mon, 29 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/how-to-break-out-of-restricted-shells-with-tcpdump/</guid>
      <description>&lt;p&gt;During security assessments we sometimes obtain access to a restricted shell on a target system. To advance further and gain complete control of the system, the next step is usually to break out of this shell. If the restricted shell provides access to certain system binaries, these binaries can often be exploited to perform such a break out. Here we would like to show an interesting example of such a break out by using the tcpdump binary.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
