3 ms·
Not the first time someone left a MongoDB database exposed to the wild, and it won't be the last. It's an easy thing to do, especially since MongoDB is so popul
by unixpickle 8y ago
Not the first time someone left a MongoDB database exposed to the wild, and it won't be the last. It's an easy thing to do, especially since MongoDB is so popular for small single-server projects.
A few years ago, I discovered the open MongoDB database of an educational website called Kaizena, which we were using in my high school English class. When I reported the problem to them, they quickly fixed it (probably with some iptables hack). They even wrote a blog post [1] about fixing it, where they claimed they added "additional firewalls to the database". More like _one_ firewall.
As a side note, Kaizena also had another security bug where their API would return JSON payloads that had private information in it (e.g. the voice feedback for other students' work). I reported it years ago, but who knows if it's fixed.
[1] https://blog.kaizena.com/post/68627783859/a-note-on-security https://blog.kaizena.com/post/68627783859/a-note-on-security
- darkarmani 8y agoFor many years Mongo would not allow you to use only Unix Domain sockets. It would always create a TCP socket as well, making it harder to secure, and nearly impossible to secure against other processes running on the server. https://stackoverflow.com/questions/21421410/how-to-disable-mongodb-tcp-port https://stackoverflow.com/questions/21421410/how-to-disable-...