<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 19 Nov 2026 19:15:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2016-10932</title>
      <link>https://127.0.0.1:10001/vuln/cve-2016-10932</link>
      <description>&lt;p&gt;An issue was discovered in the hyper crate before 0.9.4 for Rust on Windows. There is an HTTPS man-in-the-middle vulnerability because hostname verification was omitted.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the hyper crate before 0.9.4 for Rust on Windows. There is an HTTPS man-in-the-middle vulnerability because hostname verification was omitted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cve-2016-10932</guid>
    </item>
    <item>
      <title>RUSTSEC-2016-0001 — SSL/TLS MitM vulnerability due to insecure defaults</title>
      <link>https://127.0.0.1:10001/vuln/rustsec-2016-0001</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults
including off-by-default certificate verification and no API to perform hostname
verification.&lt;/p&gt;
&lt;p&gt;Unless configured correctly by a developer, these defaults could allow an attacker
to perform man-in-the-middle attacks.&lt;/p&gt;
&lt;p&gt;The problem was addressed in newer versions by enabling certificate verification
by default and exposing APIs to perform hostname verification. Use the
`SslConnector` and `SslAcceptor` types to take advantage of these new features
(as opposed to the lower-level `SslContext` type).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults
including off-by-default certificate verification and no API to perform hostname
verification.&lt;/p&gt;
&lt;p&gt;Unless configured correctly by a developer, these defaults could allow an attacker
to perform man-in-the-middle attacks.&lt;/p&gt;
&lt;p&gt;The problem was addressed in newer versions by enabling certificate verification
by default and exposing APIs to perform hostname verification. Use the
`SslConnector` and `SslAcceptor` types to take advantage of these new features
(as opposed to the lower-level `SslContext` type).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rustsec-2016-0001</guid>
    </item>
  </channel>
</rss>
