files_lock: a write-share collaborator can place a TYPE_TOKEN lock that permanently denies the file owner, survives share revocation and account delet
访问控制 / 访问控制缺陷（通用） / #3770482
该报告还没有中文解读。
原文摘录
摘自原文（7895 字符中的一小部分）
`files_lock` 33.0.4 on Nextcloud 33.0.3 lets a user with write-share permissions on someone else's file place a `TYPE_TOKEN` lock with the default infinite TTL. The lock's permission gate has no file-owner override path, no expiration, and outlives both the share and the locker's account. The …
原文中的代码
PUT /ocs/v2.php/apps/files_lock/lock/<FILE_ID>?lockType=2&format=json HTTP/1.1 Authorization: Basic bob:BobPass123x OCS-APIRequest: true
默认不展示报告全文。以上为简短摘录，完整复现过程请阅读原文。版权归研究员与 Nextcloud 所有。
时间线
- 报告提交
- 公开披露
阅读 HackerOne 原文 ↗作者 @rz1027 · 版权归作者与 Nextcloud 所有