<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Secure Disclosure on Ryan Kempt // blog</title>
    <link>https://blog.ryankempt.com/tags/secure-disclosure/</link>
    <description>Recent content in Secure Disclosure on Ryan Kempt // blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.ryankempt.com/tags/secure-disclosure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An Unauthenticated Bug in CIPP, Patched 43 Minutes After I Reported It</title>
      <link>https://blog.ryankempt.com/posts/hardening-cipp/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.ryankempt.com/posts/hardening-cipp/</guid>
      <description>&lt;p&gt;On July 14th, I found an &lt;strong&gt;unauthenticated&lt;/strong&gt; path in &lt;a href=&#34;https://cipp.app/&#34;&gt;CIPP&lt;/a&gt; to a &lt;a href=&#34;https://partner.microsoft.com/&#34;&gt;Partner Center&lt;/a&gt; token (the control plane that sits &lt;em&gt;above&lt;/em&gt; every Microsoft 365 tenant an MSP manages). I wrote up a casual security disclosure to the CyberDrain Security Team, and sent it off. Twelve minutes later I had a reply from &lt;a href=&#34;https://www.linkedin.com/in/kelvintegelaar/&#34;&gt;Kelvin Tegelaar&lt;/a&gt;. Thirty-one minutes later there was a downloadable patch and every MSP running CIPP was getting the patch.&lt;/p&gt;
&lt;p&gt;I reported it and forty-three minutes later the fix was merged, versioned, and downloadable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
