POJIA破甲
地图 / The csrf token remains same after user logs in

The csrf token remains same after user logs in

信息泄露 / 违反安全设计原则(按标题归类) / #361400

厂商
Liberapay
严重程度
未评级
赏金
—
弱点
违反安全设计原则(按标题归类)
研究员
@d4w
披露日期
2018-06-04
资产
*.liberapay.com
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(855 字符中的一小部分)
Description As the CSRF token doesn't change after login. Any other user that uses the same workstation is vulnerable. A safer way would be to use dynamic CSRF token or just change the token after login, so attacker doesn't get hold of this.

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

时间线

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

同类报告

Indexing of urls on the "External link warning" pages discloses many vulnerable endpoints from the past and unlisted videos/photosHackerOne · 2021-03-25Authorization Token on PlayStation Network Leaks via postMessage functionPlayStation · 2020-11-21 · $1,000Debug Deep Link Abuse Allows Repeated Forced Logout and Application DisruptionYelp · 2026-08-13Shopify.com Web Cache Deception vulnerability leads to personal information and CSRF tokens leakageShopify · 2021-10-21 · $800Web Cache Deception vulnerability on algolia.com leads to personal information leakageAlgolia · 2023-04-19 · $400previous token seems to work even though it does not verify emailWakaTime · 2019-11-27