mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2733] NginxProxyManager 2.0.0~2.9.19 have command execute inject vulnerability!! #1879
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1879
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LinuxProgramDevelop on GitHub (Mar 22, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2733
Describe the bug
I found a command injection vulnerability in nginx-proxy-manager, because the backend
code does not filter user input, an attacker can exploit this vulnerability to obtain
permissions, due to the different deployment methods of the old and new versions, the
corresponding container permissions/server permissions can be obtained
Nginx Proxy Manager Version
2.0.0~2.9.19
To Reproduce
report link:
github.com/LinuxProgramDevelop/NginxProxyManagerCommandInjectVulnInfo@b8c4eebbb9/Nginx_proxy_manager_Command_Inject_vulnerability.pdfExpected behavior
add a ssl cert
Operating System
docker
@blackstormlab commented on GitHub (Mar 22, 2023):
nobody except for you is supposed to access it though so while this may be possible i don't see this as anything major