POJIA破甲
地图 / OAuth2 "authorization_code" is valid indefinetly

OAuth2 "authorization_code" is valid indefinetly

身份认证 / 违反安全设计原则(按标题归类) / #1784162

厂商
Nextcloud
严重程度
低危 · CVSS 3
赏金
$100
弱点
违反安全设计原则(按标题归类)
研究员
@mikaelgundersen
披露日期
2024-02-17
资产
nextcloud/server
CVE
CVE-2024-22403

该报告还没有中文解读。

原文摘录

摘自原文(569 字符中的一小部分)
Your OAuth2 endpoint is not at all following best practices. When the authorization_code is generated it is stored without a timeout. Now according to https://www.rfc-editor.org/rfc/rfc6749#section-4.1.2 10 minutes is recommended. As the goal is that is gets used almost directly or not at all.

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

时间线

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

同类报告

Account Takeover at worki.ruMail.ru · — · $1,500Leak of authorization urls leads to account takeoverBumble · 2020-05-08Password not checked when disabling 2FA on HackerOneHackerOne · 2019-06-07Double Clickjacking Attack on WakaTime OAuth Authorization Flow at https://wakatime.com/oauth/authorizeWakaTime · 2025-08-05ABLE TO TRICK THE VICTIM INTO USING A CRAFTED EMAIL ADDRESS FOR A PARTICULAR SESSION AND THEN LATER TAKE BACK THE ACCOUNTMattermost · 2022-01-05Login page password-guessing attackRevive Adserver · 2024-04-19