Finding an IDOR in User Profile API: A $15,000 Journey to Critical
好的,用户希望我用中文帮他总结一篇文章的内容,控制在100字以内,并且不需要特定的开头。首先,我需要仔细阅读并理解文章内容。 文章主要讲述了作者发现了一个关键的不安全直接对象引用漏洞(IDOR),这个漏洞允许未经授权的用户访问任何用户的个人资料。作者通过修改API端点中的用户ID参数,成功访问、修改或删除了其他用户的私人数据。漏洞被披露后,作者获得了15,000美元的奖金,整个过程仅用了12天。 接下来,我要将这些信息浓缩到100字以内。重点包括:发现IDOR漏洞、允许访问其他用户资料、通过修改用户ID参数实现、获得奖金以及披露时间。 现在,组织语言:描述发现漏洞的方式、影响、结果和时间。确保简洁明了,不使用任何开头语。 最终总结应涵盖所有关键点,并且符合字数限制。 </think> 作者发现了一个关键的不安全直接对象引用(IDOR)漏洞,该漏洞存在于用户个人资料API端点中。通过修改用户ID参数,任何经过身份验证的用户均可查看、修改或删除其他用户的私人资料数据。该漏洞被披露后,作者获得了15,000美元的奖金,整个过程仅持续了12天。 2026-3-29 10:19:3 Author: infosecwriteups.com(查看原文) 阅读量:6 收藏

Krishna Kumar

How I discovered a critical Insecure Direct Object Reference vulnerability that allowed unauthorized access to any user profile — and how you can find similar bugs.

TL;DR: I found a critical IDOR vulnerability in a user profile API endpoint that allowed any authenticated user to view, modify, or delete any other user’s private profile data by simply changing the user ID parameter. The bug earned me a $15,000 payout after a smooth 12-day disclosure process with the vendor.

Press enter or click to view image in full size

🎯 Target & Scope

The program I was hunting on had a solid scope that included their main web application and all associated API endpoints. They specifically called out “.targetapp.com” and “.targetapp.io” as in-scope, along with their mobile API which was accessible via “api.targetapp.io”.

I always start by reading the scope three times. Sounds excessive, but I’ve missed easy wins by skimming.

The scope document mentioned they had recently launched a new profile management system as part of their platform redesign. That’s always a red flag — new code means potential security gaps.

The bounty program offered rewards from $500 (low) to $25,000 (critical), with clear severity ratings based on CVSS 3.1 scoring…


文章来源: https://infosecwriteups.com/finding-an-idor-in-user-profile-api-a-15-000-journey-to-critical-0f05e583c00b?source=rss----7b722bfd1b8d--bug_bounty
如有侵权请联系:admin#unsafe.sh