POJIA破甲
地图 / SSRF to read AWS metaData at https://█████/ [HtUS]

SSRF to read AWS metaData at https://█████/ [HtUS]

服务端请求伪造 / SSRF / #1624140

厂商
U.S. Dept Of Defense
严重程度
高危
赏金
$1,000
弱点
SSRF
研究员
@rohsec
披露日期
2022-10-14
资产
—
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(1871 字符中的一小部分)
Hello Team, While researching your program I found that the domain https://████/ is vulnerable to Server Side Request Frogery Attacks via the url parameter. An attacker is able to fetch the aws metadata abusing the SSRF at https://████████/ …
原文中的代码
ami-id
ami-launch-index
ami-manifest-path
block-device-mapping/
events/
hostname
identity-credentials/
instance-action
instance-id
instance-life-cycle
instance-type
local-hostname
local-ipv4
mac
metrics/
network/
placement/
profile
public-hostname
public-ipv4
public-keys/
reservation-id …

默认不展示报告全文。以上为简短摘录,完整复现过程请阅读原文。版权归研究员与 U.S. Dept Of Defense 所有。

时间线

  • 报告提交
  • 公开披露
阅读 HackerOne 原文 ↗作者 @rohsec · 版权归作者与 U.S. Dept Of Defense 所有

同类报告

SSRF in Exchange leads to ROOT access in all instancesShopify · 2018-05-23Server Side Request Forgery (SSRF) via Analytics ReportsHackerOne · 2023-12-08 · $25,000Server-Side Request Forgery using Javascript allows to exfill data from Google MetadataSnapchat · 2020-11-30Server Side Request Forgery (SSRF) at app.hellosign.com leads to AWS private keys disclosureDropbox · — · $4,913SSRF on project import via the remote_attachment_url on a NoteGitLab · 2020-06-07 · $10,000Server Side Request Forgery mitigation bypassGitLab · 2020-04-18