<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on GMO Flatt Security Research</title>
    <link>https://flatt.tech/research/tags/security/</link>
    <description>Recent content in Security on GMO Flatt Security Research</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://flatt.tech/research/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Poisoning Claude Code: One GitHub Issue to Break the Supply Chain</title>
      <link>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/poisoning-claude-code-one-github-issue-to-break-the-supply-chain/</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 researcher at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;After publishing my previous article ( &lt;a href=&#34;https://flatt.tech/research/research/posts/pwning-claude-code-in-8-different-ways&#34;&gt;Pwning Claude Code in 8 Different Ways&lt;/a&gt;&#xA;), I continued investigating Claude-related products and found several more vulnerabilities.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I will explain a vulnerability in Claude Code&amp;rsquo;s GitHub Actions that could allow an attacker to compromise any repository that uses the Claude Code workflow, including Anthropic&amp;rsquo;s own repositories.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Variants of the misconfiguration issues described in this article were &lt;a href=&#34;https://github.com/cline/cline/security/advisories/GHSA-9ppg-jx86-fqw7&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;actively exploited&lt;/a&gt;&#xA; &lt;a href=&#34;https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation#attack-5-ambient-codeplatform---ai-prompt-injection&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;in the wild&lt;/a&gt;&#xA; before this article was published.&lt;/p&gt;</description>
    </item>
    <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>Pwning Claude Code in 8 Different Ways</title>
      <link>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</link>
      <pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/pwning-claude-code-in-8-different-ways/</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 few months ago, I came across an interesting behavior while using Claude Code—it executed a command without my approval.&lt;/p&gt;&#xA;&lt;p&gt;Since I wasn&amp;rsquo;t using the permission bypass mode, I decided to investigate further to understand why it was able to execute commands without explicit approval.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;I discovered 8 ways to execute arbitrary commands in Claude Code without user approval.&lt;/p&gt;</description>
    </item>
    <item>
      <title>LLM App Security: Risk &amp; Prevent for GenAI Development</title>
      <link>https://flatt.tech/research/posts/llm-application-security/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/llm-application-security/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m Sato (&lt;a href=&#34;https://x.com/Nick_nick310&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@Nick_nick310&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In recent years, the evolution and widespread adoption of Large Language Models (LLM) have been remarkable, and they are being utilized as generative AI in many services and business processes. While LLMs bring significant benefits, new security risks stemming from their characteristics have also been pointed out, making sufficient understanding and countermeasures essential for safe utilization. What kind of security challenges might arise when integrating LLMs into your company&amp;rsquo;s services and operations?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Securing LLM Function-Calling: Risks &amp; Mitigations for AI Agents</title>
      <link>https://flatt.tech/research/posts/securing-llm-function-calling/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/securing-llm-function-calling/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello. I’m Yamakawa (&lt;a href=&#34;https://x.com/dai_shopper3&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@dai_shopper3&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security, Inc.&lt;/p&gt;&#xA;&lt;p&gt;LLMs exhibit high capabilities in various applications such as text generation, summarization, and question answering, but they have several limitations when used alone. Fundamentally, a standalone model only has the function of generating strings in response to input natural language. Therefore, to create an autonomous AI based on an LLM, a means to exchange information with the outside and execute concrete actions is necessary.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Risks of LLM Frameworks with Case Studies</title>
      <link>https://flatt.tech/research/posts/llm-framework-vulns-exposed/</link>
      <pubDate>Wed, 29 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/llm-framework-vulns-exposed/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hello. I’m Mori (&lt;a href=&#34;https://twitter.com/ei01241&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@ei01241&lt;/a&gt;&#xA;), a security engineer at GMO Flatt Security, Inc.&lt;/p&gt;&#xA;&lt;p&gt;In recent years, the evolution of Large Language Models (LLMs) has accelerated the development of a wide range of AI applications, such as chatbots, data analysis/summarization, and autonomous agents. &lt;strong&gt;LLM frameworks&lt;/strong&gt; like LangChain and LlamaIndex abstract LLM collaboration and external data connections to improve development efficiency, but behind this convenience lie new security risks.&lt;/p&gt;&#xA;&lt;p&gt;In this article, we will explain common vulnerabilities that tend to occur when using or developing LLM frameworks, illustrated with specific CVEs, and learn lessons from each vulnerability. We will also introduce countermeasures that developers should be aware of based on these lessons.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2025-59489: Arbitrary Code Execution in Unity Runtime</title>
      <link>https://flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/</link>
      <pubDate>Fri, 03 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/arbitrary-code-execution-in-unity-runtime/</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;In May 2025, I participated in the &lt;a href=&#34;https://www.youtube.com/watch?v=jiLeF0zO8Mg&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Meta Bug Bounty Researcher Conference 2025.&lt;/a&gt;&#xA;&#xA;During this event, I discovered a vulnerability (CVE-2025-59489) in the Unity Runtime that affects games and applications built on Unity 2017.1 and later.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I will explain the technical aspects of this vulnerability and its impact.&lt;/p&gt;&#xA;&lt;p&gt;This vulnerability was disclosed to Unity following responsible disclosure practices.&lt;br&gt;&#xA;Unity has since released patches for Unity 2019.1 and later, as well as a Unity Binary Patch tool to address the issue, and I strongly encourage developers to download the updated versions of Unity, recompile affected games or applications, and republish as soon as possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why XSS Persists in This Frameworks Era?</title>
      <link>https://flatt.tech/research/posts/why-xss-persists-in-this-frameworks-era/</link>
      <pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/why-xss-persists-in-this-frameworks-era/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Hi, I&amp;rsquo;m canalun (&lt;a href=&#34;https://x.com/i_am_canalun&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@i_am_canalun&lt;/a&gt;&#xA;), a security researcher at GMO Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;This article explores the question: &amp;ldquo;Why Does XSS Still Occur So Frequently?&amp;rdquo; We will delve into why this notorious and classic vulnerability despite the widespread adoption of built-in XSS countermeasures in modern development frameworks.&lt;/p&gt;&#xA;&lt;p&gt;The world of web development, especially frameworks, is evolving at a rapid pace, bringing improvements not only in development efficiency but also in security.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Achieving RCE in famous Japanese chat tool with an obsolete Electron feature</title>
      <link>https://flatt.tech/research/posts/escaping-electron-isolation-with-obsolete-feature/</link>
      <pubDate>Wed, 19 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/escaping-electron-isolation-with-obsolete-feature/</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;A while ago, I &lt;a href=&#34;https://jvn.jp/en/jp/JVN78335885/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;reported a remote code execution vulnerability&lt;/a&gt;&#xA; that chains multiple problems in Chatwork, a popular communication tool in Japan.&lt;/p&gt;&#xA;&lt;p&gt;In the report that I sent to the bug bounty platform, I used an obsolete feature of Electron to escalate to the preload context.&lt;br&gt;&#xA;As the vulnerability was interesting, I&amp;rsquo;m writing this article to share the details of it.&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>
    <item>
      <title>Non-Intrusive Web Recon: Techniques from Chrome DevTools Recorder</title>
      <link>https://flatt.tech/research/posts/non-intrusive-web-recon-techniques-from-chrome-devtools-recorder/</link>
      <pubDate>Wed, 25 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/non-intrusive-web-recon-techniques-from-chrome-devtools-recorder/</guid>
      <description>&lt;h2 id=&#34;introduction-the-art-of-non-intrusive-web-recon&#34;&gt;Introduction: The Art of Non-Intrusive Web Recon&lt;/h2&gt;&#xA;&lt;p&gt;Hello, I&amp;rsquo;m pizzacat83 (&lt;a href=&#34;https://twitter.com/pizzacat83&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@pizzacat83&lt;/a&gt;&#xA;), a software engineer at Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;When hunting for bugs, understanding the behavior of a target application is invaluable. The more knowledge you gain about the application—where each functionality resides, how pages and APIs interconnect—the greater your ability to pinpoint weaknesses and unravel vulnerabilities.&lt;/p&gt;&#xA;&lt;p&gt;Imagine a tool that could seamlessly assist with this process, extracting key insights from the browser in real-time as you navigate through the application. A tool that, while you click through the interface, captures the underlying DOM structure, traces interactions, and reveals valuable data connections—all without disrupting your flow. This would make it possible to map the application’s behavior as you go, without needing to slow down to document every detail manually.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Compromising OpenWrt Supply Chain via Truncated SHA-256 Collision and Command Injection</title>
      <link>https://flatt.tech/research/posts/compromising-openwrt-supply-chain-sha256-collision/</link>
      <pubDate>Fri, 06 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/compromising-openwrt-supply-chain-sha256-collision/</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 Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;A few days ago, I was upgrading my home lab network, and I decided to upgrade the &lt;a href=&#34;https://openwrt.org/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;OpenWrt&lt;/a&gt;&#xA; on my router.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; After accessing the LuCI, which is the web interface of OpenWrt, I noticed that there is a section called &lt;code&gt;Attended Sysupgrade&lt;/code&gt;, so I tried to upgrade the firmware using it.&lt;/p&gt;&#xA;&lt;p&gt;After reading the description, I found that it states it builds new firmware using an online service.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Beyond the Limit: Expanding single-packet race condition with a first sequence sync for breaking the 65,535 byte limit</title>
      <link>https://flatt.tech/research/posts/beyond-the-limit-expanding-single-packet-race-condition-with-first-sequence-sync/</link>
      <pubDate>Fri, 02 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/beyond-the-limit-expanding-single-packet-race-condition-with-first-sequence-sync/</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 Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In 2023, &lt;a href=&#34;https://twitter.com/albinowax&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;James Kettle&lt;/a&gt;&#xA; of PortSwigger published &lt;a href=&#34;https://portswigger.net/research/smashing-the-state-machine&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;an excellent paper&lt;/a&gt;&#xA; titled &lt;code&gt;Smashing the state machine: the true potential of web race conditions&lt;/code&gt;.&lt;br&gt;&#xA;In the paper, he introduced a new attack technique called single-packet attack that can exploit a race condition without being affected by the network jitter.  &lt;/p&gt;&#xA;&lt;figure&gt;&#xA;  &lt;img src=&#34;https://flatt.tech/research/research/beyond-the-limit-expanding-single-packet-race-condition-with-first-sequence-sync/01.png&#34; alt=&#34;An image that indicates single-packet bypasses the network jitter&#34;&gt;&#xA;  &lt;center&gt;&lt;figcaption&gt;Quoted from &lt;a href=&#34;https://portswigger.net/research/smashing-the-state-machine&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Smashing the state machine: the true potential of web race conditions&lt;/a&gt;&lt;/figcaption&gt;&lt;/center&gt;&#xA;&lt;/figure&gt;&#xA;&lt;p&gt;Recently, I encountered a limit-overrun type of race condition that requires sending approximately 10,000 requests simultaneously to exploit reliably, so I attempted to apply the single packet attack to it.&lt;br&gt;&#xA;However, due to the single packet attack&amp;rsquo;s limitation, which restricts the maximum size of requests that can be sent to around 1,500 bytes, I couldn&amp;rsquo;t exploit the vulnerability.  &lt;/p&gt;</description>
    </item>
    <item>
      <title>BatBadBut: You can&#39;t securely execute commands on Windows</title>
      <link>https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/</link>
      <pubDate>Tue, 09 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/</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 Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;Recently, I reported multiple vulnerabilities to several programming languages that allowed an attacker to perform command injection on Windows when the specific conditions were satisfied.&lt;br&gt;&#xA;Today, &lt;a href=&#34;https://kb.cert.org/vuls/id/123335&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;affected vendors published advisories of these vulnerabilities&lt;/a&gt;&#xA;, so I&amp;rsquo;m documenting the details here to provide more information about the vulnerabilities and minimize the confusion regarding the high CVSS score.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;strong&gt;BatBadBut&lt;/strong&gt; is a vulnerability that allows an attacker to perform command injection on Windows applications that indirectly depend on the &lt;code&gt;CreateProcess&lt;/code&gt; function when the specific conditions are satisfied.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Finding bugs to trigger Unauthenticated Command Injection in a NETGEAR router (PSV-2022–0044)</title>
      <link>https://flatt.tech/research/posts/finding-bugs-to-trigger-unauthenticated-command-injection-in-a-netgear-router-psv-2022-0044/</link>
      <pubDate>Sat, 26 Mar 2022 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/finding-bugs-to-trigger-unauthenticated-command-injection-in-a-netgear-router-psv-2022-0044/</guid>
      <description>&lt;h2 id=&#34;preface&#34;&gt;Preface&lt;/h2&gt;&#xA;&lt;p&gt;Hi, I’m stypr (&lt;a href=&#34;https://twitter.com/stereotype32&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@stereotype32&lt;/a&gt;&#xA; ) from Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;Last year, I wrote a blog post about technical explanations about 0days found in Japanese OSS products.&lt;/p&gt;&#xA;&lt;p&gt;I have found a lot of vulnerabilities in various products since then. Unfortunately, most bugs I found did not get it fixed right away, so I did not get any chances to share some exciting vulnerabilities I found until today.&lt;/p&gt;&#xA;&lt;p&gt;This article will explain how I found various vulnerabilities and chained some of the vulnerabilities into an unauthenticated command execution without any preconditions in a NETGEAR’s WAC124(AC2000) router.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Finding an unseen SQL Injection by bypassing escape functions in mysqljs/mysql</title>
      <link>https://flatt.tech/research/posts/finding-an-unseen-sql-injection-by-bypassing-escape-functions-in-mysqljs-mysql/</link>
      <pubDate>Tue, 22 Feb 2022 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/finding-an-unseen-sql-injection-by-bypassing-escape-functions-in-mysqljs-mysql/</guid>
      <description>&lt;h2 id=&#34;tldr&#34;&gt;TL;DR&lt;/h2&gt;&#xA;&lt;p&gt;It was found that unexpected behaviors in the query’s escape function could cause a SQL injection in &lt;code&gt;mysqljs/mysql&lt;/code&gt; (&lt;a href=&#34;https://github.com/mysqljs/mysql&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;https://github.com/mysqljs/mysql&lt;/a&gt;&#xA;), which is one of the most popular MySQL packages in the Node.js ecosystem.&lt;/p&gt;&#xA;&lt;p&gt;Typically, query escape functions or placeholders are known to prevent SQL injections. However, &lt;code&gt;mysqljs/mysql&lt;/code&gt; is known to have different escape methods over different value types, and it could eventually cause unexpected behaviors when the attacker passes the parameter with a different value type. Unexpected behaviors include buggy behaviors and SQL injections.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2020–15702 Race Condition vulnerability in handling of PID by apport</title>
      <link>https://flatt.tech/research/posts/race-condition-vulnerability-in-handling-of-pid-by-apport/</link>
      <pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/race-condition-vulnerability-in-handling-of-pid-by-apport/</guid>
      <description>&lt;p&gt;Note) It’s just an English version of &lt;a href=&#34;https://flattsecurity.hatenablog.com/entry/2020/09/15/190029&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;previous post&lt;/a&gt;&#xA;.&lt;/p&gt;&#xA;&lt;p&gt;Hello, I’m Shiga( &lt;a href=&#34;https://twitter.com/Ga_ryo_&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@Ga_ryo_&lt;/a&gt;&#xA; ), a security engineer at Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I would like to give you a technical description of &lt;a href=&#34;https://nvd.nist.gov/vuln/detail/CVE-2020-15702&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CVE-2020–15702&lt;/a&gt;&#xA; which is published recently. I discovered this vulnerability and reported it to the vendor via the &lt;a href=&#34;https://www.zerodayinitiative.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Zero Day Initiative&lt;/a&gt;&#xA;. This article is not intended to inform you of the dangers of vulnerabilities, but to share tips from a technical point of view.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CVE-2021–20226 a reference counting bug which leads to local privilege escalation in io_uring</title>
      <link>https://flatt.tech/research/posts/a-reference-counting-bug-which-leads-to-local-privilege-escalation-in-io-uring/</link>
      <pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate>
      <guid>https://flatt.tech/research/posts/a-reference-counting-bug-which-leads-to-local-privilege-escalation-in-io-uring/</guid>
      <description>&lt;p&gt;Hello, I’m Shiga( &lt;a href=&#34;https://twitter.com/Ga_ryo_&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;@Ga_ryo_&lt;/a&gt;&#xA; ), a security engineer at Flatt Security Inc.&lt;/p&gt;&#xA;&lt;p&gt;In this article, I would like to give you a technical description of CVE-2021–20226( &lt;a href=&#34;https://www.zerodayinitiative.com/advisories/ZDI-21-001/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;ZDI-2021–001&lt;/a&gt;&#xA; ) which is published before. I discovered this vulnerability and reported it to the vendor via the Zero Day Initiative. This article is not intended to inform you of the dangers of vulnerabilities, but to share tips from a technical point of view.&lt;/p&gt;&#xA;&lt;p&gt;An overview of the vulnerabilities and attack methods can be found at the links below. This blog will explain in a little more detail.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
