Summarize the following in 10 bullet points.
Title: "Are small tools safe enough for self-hosting? - YouTube"
Transcript: "so I've been running home labs for several years now using all sorts of software projects to self-host stuff like proxmox Docker kubernetes Homeland dashboards and monitoring you all know this from my videos and I often love to use even smaller software projects like the nginx proxy manager for instance which I was using as a secure web proxy to protect some of my web services with https and trusted TLS certificate actually a nice project but just recently something happened that made me question this decision and once I looked further into it I was shocked by how many problems this particular project has and that got me thinking well maybe small software projects like this aren't safe enough for self-hosting is that really true let's talk about that it all started with a message by one of our community members on our Discord pointing out the number of a common vulnerability and exposure cve in nginx proxy manager note this particular cve describes an OS Commander injection so whenever you're creating an access list an authenticated attacker would be able to execute arbitrary commands to the operating system which potentially could cause some damage take over the system and yeah many other bad things and it's also made clear that this problem is not part of the nginx software itself but caused by a bad implementation of the nginx proxy manager team and first I wasn't really too worried about that to be honest because you know cves are reported every day even on bigger software projects it's just part of the game what really warped me was once I looked up the history of this report and I found out this cve was just the tip of the iceberg but let's get into it so now originally this issue was reported by NAME_1 who raised an issue on the nginx proxy manager repository on GitHub on May the 21st in 2022 that was already the past year and he is basically saying someone in his security kubernet he found a potential issue in nginx proxy manager which he would like to report however the repository on GitHub was missing the security. md file which contains the information about how to contact the developers in such a case so there was no information where to send this report to and I guess not everybody here is familiar with the process of how security vulnerabilities are usually reported it's very similar to what just happened here when you find a security vulnerability somewhere in an application First repeat the request without change, then give your answer.
user