POJIA破甲
地图 / PURGE is not authenticated

PURGE is not authenticated

身份认证 / 认证缺陷(通用) / #629612

厂商
Yelp
严重程度
低危
赏金
—
弱点
认证缺陷(通用)
研究员
@rac_fckscty
披露日期
2023-01-19
资产
—
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(2191 字符中的一小部分)
Anyone can issue a PURGE request for any resource and invalidate your caches. That can lead to increased bandwidth costs.
原文中的代码
E:\>curl https://s3-media0.fl.yelpcdn.com/assets/public/[email protected]_design_web.yji-629fce3629585b9db2137d9353196628.png --head
HTTP/1.1 200 OK
ETag: "629fce3629585b9db2137d9353196628"
x-amz-version-id: KnfcY6QenKubeC6DBXpUT1d87B17ORdD
Content-Type: image/png
Server: AmazonS3
Via: 1.1 varnish …

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

时间线

  • 报告提交
  • 公开披露
阅读 HackerOne 原文 ↗作者 @rac_fckscty · 版权归作者与 Yelp 所有

同类报告

Improper Authentication - any user can login as other user with otp/logout & otp/loginSnapchat · 2021-09-03Bypassing Digits origin validation which leads to account takeoverX / xAI · 2020-06-24Flickr Account Takeover using AWS Cognito APIFlickr · 2021-12-18Chained Bugs to Leak Victim's Uber's FB Oauth TokenUber · 2019-01-25[cs.money] Open Redirect Leads to Account TakeoverCS Money · 2020-09-30OTP token bypass in accessing user settingsRazer · — · $1,000