POJIA破甲
地图 / SSRF via User-Controlled Push proxyServer in Notifications Push Registration

SSRF via User-Controlled Push proxyServer in Notifications Push Registration

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

厂商
Nextcloud
严重程度
低危 · CVSS 5.4
赏金
—
弱点
SSRF
研究员
@yoyomiski
披露日期
2026-09-30
资产
nextcloud/notifications
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(3637 字符中的一小部分)
Summary: An authenticated low-privilege user can register a push device with an attacker-controlled `proxyServer` through `POST /ocs/v2.php/apps/notifications/api/v2/push` Later, when a notification is triggered for that user, the backend performs a server-side POST request to …
原文中的代码
- notifications-master\lib\Controller\PushController.php (accepts user proxyServer, NoAdminRequired route)
- notifications-master\lib\Push.php (sendNotificationsToProxies(), server-side POST $proxyServer.'/notifications')

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

时间线

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

同类报告

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