IT之家 9 月 28 日消息,16 岁安全研究员 Faav 于当地时间 9 月 25 日在其主页发布博客,披露了关于他如何发现微软内部漏洞并取得 5,000 美元(IT之家注:现汇率约合 33,597 元人民币)漏洞赏金的经历。
他发现,微软内部分析平台 Titan 存在身份验证漏洞,黑客可藉此访问包含约 2.5 万条员工数据记录的内部数据库,并能查询总量达 17.3 万亿条的数据记录。
Faav 称,他自 15 岁起参与漏洞赏金项目,并开发了 AI 机器人 Antares。2026 年 8 月 25 日,Antares 发现 Titan 的公开 API 接口。该接口提示需要连接 VPN,Faav 随后让 Antares 枚举相关子域名,发现一个位于 Azure 云环境中的主机,并找到对应的 Swagger / OpenAPI 文件。
这份文件列出了 4 个 API 路由。其中 3 个要求 Azure Active Directory 身份验证,但最后一个名为“/v2/Query”的接口没有这一要求,而且兼容直接提交 SQL 查询。
Faav 仍需要了解数据库结构。他借助 Wayback Machine 找到了 2023 年 Titan 登录页快照,并从其中获取到了 Apache Superset 规格文件(该文件描述了数据库结构,共包含 56 个数据表定义)。
Antares 随后用 10 天探测 JWT 验证流程。随后,Faav 发现“/v2/Query”接口虽然要求 JWT 身份验证,但服务器似乎没有校验令牌的数字签名。后续,他依据服务器返回方式产生判断,伪造了一枚 alg 为 none、签名段为空的登录令牌,将 upn 改为 admin 后,成功以管理员身份执行 SQL。
9 月 5 日凌晨,他确认可访问 Titan 平台的数据库。查询表明,其元数据包含约 25000 个账户与邮箱记录、17990 个员工邮箱记录、15001 个员工组织记录,以及 355 个数据库规格、20979 个虚拟数据集 SQL 定义、24569 个仪表盘和 425891 个图表。
继续检查后,他在数据库中还发现了一组与 Bing 分析相关的数据源。借助汇总多个数据表中的记录数量,Faav 估算自己可访问的数据规模达到 17,333,335,124,315 条。
Faav 表示,他在凌晨 2 点发现这一数字时,为避免吵醒父母,还不得不克制住喊出来的冲动。随后,他将开始撰写报告并向微软 MSRC 提交。
微软在 9 月 6 日至 8 日要求他停止测试并给出 IP 地址,以确认无超出安全研究的活动。9 月 9 日,该 API 接口即被锁定。
9 月 17 日,微软向 Faav 颁发 5,000 美元(现汇率约合 33,597 元人民币)赏金。9 月 22 日,双方会面讨论漏洞并协调披露。Faav 称,微软在博客发布前对文章开展了编辑控制,删减部分内容并调整影响描述。
微软在声明中表示:“笔者感谢有机会调查 Faav 报告的发现。其提交和协调漏洞披露协助笔者更好地保护客户,强化了服务。”微软强调,该公司将继续重视在漏洞赏金计划下的安全研究。
本文来源:https://www.ithome.com/1/008/000.htm
若有版权问题,请来信告知:13951431913#139.com 或在右方提交评论。
IT Home, September 28 - 16-year-old security researcher Faav published a blog post on his homepage on September 25 local time, disclosing how he discovered an internal Microsoft vulnerability and earned a $5,000 (IT Home note: approximately 33,597 RMB at the current exchange rate) bug bounty.
He found that Microsoft's internal analysis platform Titan had an authentication vulnerability, through which hackers could access an internal database containing approximately 25,000 employee data records, and could query a total of 17.3 trillion data records.
Faav said he has been participating in bug bounty programs since age 15 and developed the AI bot Antares. On August 25, 2026, Antares discovered Titan's public API endpoint. The endpoint indicated that a VPN connection was required. Faav then had Antares enumerate related subdomains, found a host in the Azure cloud environment, and located the corresponding Swagger/OpenAPI file.
This file listed 4 API routes. Three of them required Azure Active Directory authentication, but the last one, an endpoint named "/v2/Query", did not have this requirement and supported direct submission of SQL queries.
Faav still needed to understand the database structure. Using the Wayback Machine, he found a snapshot of the Titan login page from 2023 and obtained the Apache Superset specification file from it (this file described the database structure and contained a total of 56 data table definitions).
Antares then spent 10 days probing the JWT verification process. Subsequently, Faav discovered that although the "/v2/Query" endpoint required JWT authentication, the server did not seem to verify the token's digital signature. Later, based on his judgment formed from the server's response behavior, he forged a login token with alg set to none and an empty signature segment. After changing upn to admin, he successfully executed SQL as an administrator.
In the early morning of September 5, he confirmed he could access the Titan platform's database. Queries showed that its metadata contained approximately 25,000 account and email records, 17,990 employee email records, 15,001 employee organization records, as well as 355 database specifications, 20,979 virtual dataset SQL definitions, 24,569 dashboards, and 425,891 charts.
After continued inspection, he also found a set of data sources related to Bing analytics in the database. By aggregating the record counts in multiple data tables, Faav estimated that the scale of data he could access reached 17,333,335,124,315 records.
Faav said that when he discovered this number at 2 a.m., he had to restrain his urge to shout in order to avoid waking his parents. He then began writing a report and submitted it to Microsoft MSRC.
From September 6 to 8, Microsoft asked him to stop testing and provide his IP address to confirm there was no activity beyond security research. On September 9, the API endpoint was locked down.
On September 17, Microsoft awarded Faav a $5,000 (approximately 33,597 RMB at the current exchange rate) bounty. On September 22, the two sides met to discuss the vulnerability and coordinate disclosure. Faav said Microsoft exercised editorial control over the article before publication, cutting some content and adjusting the impact description.
Microsoft said in a statement: "We appreciate the opportunity to investigate the findings reported by Faav. Their submission and coordinated vulnerability disclosure helped us better protect customers and strengthen our services." Microsoft emphasized that it will continue to value security research under the bug bounty program.
