GraphQL Security: How I Found and Exploited Critical IDOR and Authorization Bypass in a…
好的,我现在需要帮用户总结一篇英文文章的内容,控制在100个字以内。用户已经提供了文章的标题和部分内容,看起来是关于安全研究人员通过发现GraphQL漏洞赚取赏金的故事。 首先,我得理解文章的主要内容。作者在 fintech 公司的API中发现了GraphQL introspection和batch query漏洞,利用这些漏洞访问和修改了其他用户的财务交易,获得了高CVSS评分和12500美元的赏金。 接下来,我要用简洁的语言概括这些要点。需要注意的是,用户要求不要以“文章内容总结”等开头,直接写描述即可。同时,控制在100字以内。 可能的结构是:研究人员发现漏洞、利用漏洞进行攻击、获得奖励。这样既涵盖了主要事件,又符合字数限制。 现在,我需要将这些信息整合成一个连贯的句子。例如:“研究人员通过发现GraphQL introspection和batch query漏洞,在fintech公司的API中获取了高权限,并修改了其他用户的交易,获得了12500美元的赏金。” 检查一下是否符合要求:没有使用开头语,内容准确,字数控制在100字以内。看起来没问题。 </think> 研究人员通过发现GraphQL introspection和batch query漏洞,在fintech公司的API中获取了高权限,并修改了其他用户的交易,获得了12500美元的赏金。 2026-4-4 10:31:44 Author: infosecwriteups.com(查看原文) 阅读量:15 收藏

Krishna Kumar

How I earned $12,500 finding GraphQL introspection and batch query vulnerabilities in a fintech startup’s API infrastructure

TL;DR: During a bug bounty engagement on a fintech target, I discovered that GraphQL introspection was publicly enabled, allowing full schema enumeration. By exploiting batch query processing and an Insecure Direct Object Reference (IDOR) vulnerability, I was able to access and modify other users’ financial transactions. The vulnerability earned a CVSS 9.1 score and a $12,500 payout.

Press enter or click to view image in full size

🎯 Target & Scope — Finding My Prey

Let me set the stage for you. It was a typical Tuesday night, coffee brewing, and I was scrolling through HackerOne looking for my next target. That’s when I saw a private program — let’s call them “FinanceFlow” (fictional name) — a growing fintech startup handling payment processing for small businesses.

The program had a solid scope: web application, mobile API, and importantly — a GraphQL API endpoint listed explicitly. Most hunters overlook GraphQL, which is exactly why I got excited. Uncharted territory means less competition and higher chances of finding something juicy.


文章来源: https://infosecwriteups.com/graphql-security-how-i-found-and-exploited-critical-idor-and-authorization-bypass-in-a-42ab78e13642?source=rss----7b722bfd1b8d--bug_bounty
如有侵权请联系:admin#unsafe.sh