[Bug] 警惕ChatGPT-Next-Web可能的安全漏洞

[tiyee]

为了提高交流效率，我们设立了官方 QQ 群和 QQ 频道，如果你在使用或者搭建过程中遇到了任何问题，请先第一时间加群或者频道咨询解决，除非是可以稳定复现的 Bug 或者较为有创意的功能建议，否则请不要随意往 Issue 区发送低质无意义帖子。

点击加入官方群聊

反馈须知

⚠️ 注意：不遵循此模板的任何帖子都会被立即关闭，如果没有提供下方的信息，我们无法定位你的问题。

请在下方中括号内输入 x 来表示你已经知晓相关内容。

• 我确认已经在 常见问题 中搜索了此次反馈的问题，没有找到解答；
• 我确认已经在 Issues 列表（包括已经 Close 的）中搜索了此次反馈的问题，没有找到解答。
• 我确认已经在 Vercel 使用教程 中搜索了此次反馈的问题，没有找到解答。

描述问题
昨天我部署的ChatGPT-Next-Web被刷，通过NGINX访问日志，确定确实是从ChatGPT-Next-Web页面操作的。对方是俄罗斯圣彼得堡的ip.聊天内容是俄文

我的ChatGPT-Next-Web是通过docker compose部署，部署在阿里云上。设置了code访问密码，而且半个月前刚换过，当初考虑到安全问题，我的ChatGPT的key写死在我的代理程序里，代理程序是我自己用go开发的。ChatGPT-Next-Web只能通过内部的容器IP访问，根本没有暴露出去。我的docker-compose.yml文件如下：

个人猜猜，Next可能有漏洞可以绕过页面密码。当然对方是如何找到我部署的项目地址的，则可能是通过搜索引擎通过next的特征链接或页面关键字搜出来的。
当然，以上也只是猜测，加上我的ChatGPT有限额，所以被刷的金额也不多，但是希望引起大家的小心。
目前比较好的措施，是在NGINX里加上auth_basic密码，另外，可以取消项目域名的公网dns解析，通过改本地hosts访问。

如何复现
请告诉我们你是通过什么操作触发的该问题。

截图
截图见上文

一些必要的信息

• 系统：[CentOS stream 9]
• 浏览器： [firefoox]
• 版本： [2.9.11]
• 部署方式：[docker ]

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug] Be wary of possible security vulnerabilities in ChatGPT-Next-Web

In order to improve communication efficiency, we have set up an official QQ group and QQ channel. If you encounter any problems during use or construction, please join the group or channel for consultation as soon as possible, unless it is a bug that can be stably reproduced or More creative feature suggestions, otherwise please do not send low-quality and meaningless posts to the Issue area.

Click to join the official group chat

Feedback Instructions

⚠️ NOTE: Any post that does not follow this template will be immediately closed and we will not be able to locate your issue without providing the information below.

Please enter x in the square brackets below to indicate that you already know the relevant content.

• I confirm that I have searched for the feedback issue in FAQ. No solution found;
• I confirm that I have searched the Issues list (including those that have been Closed) for this feedback issue, but no answer has been found.
• I confirm that I have searched for the feedback issue in Vercel usage tutorial , no answer found.

Describe the problem
Yesterday, the ChatGPT-Next-Web I deployed was brushed. Through the NGINX access log, I confirmed that it was indeed operated from the ChatGPT-Next-Web page. The other party is an IP address in St. Petersburg, Russia. The chat content is in Russian.

My ChatGPT-Next-Web is deployed through docker compose and deployed on Alibaba Cloud. I set a code access password and just changed it half a month ago. Considering security issues, my ChatGPT key was hard-coded in my agent program. The agent program was developed by myself using Go. ChatGPT-Next-Web can only be accessed through the internal container IP and is not exposed at all. My docker-compose.yml file is as follows:

My personal guess is that Next may have a loophole that can bypass the page password. Of course, how the other party found the address of the project I deployed may be through a search engine through next feature links or page keywords.
Of course, the above is just a guess. In addition, my ChatGPT has a limit, so the amount of money that was swiped is not much, but I hope everyone will be careful.
A better measure at present is to add the auth_basic password to NGINX. In addition, you can cancel the public network dns resolution of the project domain name and access it by changing local hosts.

How ​​to reproduce
Please tell us what action triggered this issue.

screenshot
See screenshot above

Some necessary information

• System: [CentOS stream 9]
• Browser: [firefoox]
• Version: [2.9.11]
• Deployment method: [docker]

[Yidadaa]

请提供进一步的 ChatGPT Next Web Docker 内部日志来辅助定位原因，来确认是否真的绕过了密码机制。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Please provide further ChatGPT Next Web Docker internal logs to help locate the cause and confirm whether the password mechanism is really bypassed.

[H0llyW00dzZ]

maybe that cause of disableFastLink is not set true so it can be possible to bypass