<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Git on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/git/</link>
    <description>Recent content in Git on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote Command Execution in Google Cloud with Single Directory Deletion</title>
      <link>https://flatt.tech/research/posts/remote-command-execution-in-google-cloud-with-single-directory-deletion/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/remote-command-execution-in-google-cloud-with-single-directory-deletion/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m &lt;a href=&#34;https://ryotak.net&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;RyotaK&lt;/a&gt;&#xA; (&lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A while ago, I participated in the &lt;a href=&#34;https://bughunters.google.com/blog/5364401980899328/hardening-google-cloud-insights-from-the-latest-cloud-vrp-bugswat&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Google Cloud VRP bugSWAT,&lt;/a&gt;&#xA; a live hacking event organized by Google.&lt;/p&gt;&#xA;&lt;p&gt;During this event, I discovered a remote command execution vulnerability in one of Google Cloud&amp;rsquo;s services. As the vulnerability has now been fixed, I would like to share the technical details in this article.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;Google Cloud has a product called Looker, and this product has a feature to manage Git repositories.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clone2Leak: Your Git Credentials Belong To Us</title>
      <link>https://flatt.tech/research/posts/clone2leak-your-git-credentials-belong-to-us/</link>
      <pubDate>Sun, 26 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/clone2leak-your-git-credentials-belong-to-us/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m RyotaK ( &lt;a href=&#34;https://twitter.com/ryotkak&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ryotkak&lt;/a&gt;&#xA; ), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In October 2024, I was hunting bugs for the GitHub Bug Bounty program. After investigating GitHub Enterprise Server for a while, I felt bored and decided to try to find bugs on GitHub Desktop instead.&lt;/p&gt;&#xA;&lt;p&gt;After reading the source code of GitHub Desktop, I found a bug that allows a malicious repository to leak the user&amp;rsquo;s credentials.&lt;br&gt;&#xA;Since the concept of the bug is interesting, I decided to investigate other Git-related projects and found many bugs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
