No, some things are better left unknown.
Database leak exposes 3.3M Hello Kitty fans
11–20 of 57 posts
Re: Database leak exposes 3.3M Hello Kitty fans
#12> Update 2: Earlier this afternoon, Chris Vickery confirmed that the three IP addresses that were disclosing user information have been secured. The issue wasn't a hack, but a misconfigured MongoDB installation. > The source of the configuration error isn't clear, as neither the ISP nor Sanrio has answered questions on the matter. A MongoDB database open to the outside world on a public IP address?
i.e. the default configuration But yeah, that's not good.
The default configuration for MongoDB is to listen on localhost only. Someone changed the configuration if it was listening on a public IP.
Re: Database leak exposes 3.3M Hello Kitty fans
#13Evening project: union Hello Kitty and Ashley Madison lists. No, some things are better left unknown.
Re: Database leak exposes 3.3M Hello Kitty fans
#14Earlier quoted context omitted.
i.e. the default configuration But yeah, that's not good.
> i.e. the default configuration The default configuration for MongoDB is to listen on localhost only. Someone changed the configuration if it was listening on a public IP.
That's true, but I remember that change was only made recently. Before, mongo would listen on all IPs and had no passwords.
Re: Database leak exposes 3.3M Hello Kitty fans
#15> Update 2: Earlier this afternoon, Chris Vickery confirmed that the three IP addresses that were disclosing user information have been secured. The issue wasn't a hack, but a misconfigured MongoDB installation. > The source of the configuration error isn't clear, as neither the ISP nor Sanrio has answered questions on the matter. A MongoDB database open to the outside world on a public IP address?
These things happen to the best: In 2001, the World Economic Forum had their MS-SQLServer with personal data of the participants connected to the Internet. With the standard account enabled (user: "sa", password: empty). It then got "hacked" and the data leaked. German article about it: https://www.woz.ch/-41f8
1. There is no password prompt during installation. This was the same problem many relational databases had back in the day with default user credentials. Today, I don't know of a single relational datastore that comes with default credentials during installation. (ignoring things that shouldn't go to production like homebrew) Individually, they all said it was a "security threat" and did something about it.
2. Things like MMS or other offering from MongoDB itself expect you expose your nodes externally so they can manage things for you. This can easily be made secure... but its contradictory in nature. It suggests to somebody who probably doesn't know what they're doing on the IT or DevOps fronts to do something more easily dangerous than not... just so they can sell their vendor services to you. Its a recipe for disaster but its also easily fixable with a few design changes on their side.
Re: Database leak exposes 3.3M Hello Kitty fans
#16Evening project: union Hello Kitty and Ashley Madison lists. No, some things are better left unknown.
Re: Database leak exposes 3.3M Hello Kitty fans
#17Evening project: union Hello Kitty and Ashley Madison lists. No, some things are better left unknown.
Re: Database leak exposes 3.3M Hello Kitty fans
#18> Update 2: Earlier this afternoon, Chris Vickery confirmed that the three IP addresses that were disclosing user information have been secured. The issue wasn't a hack, but a misconfigured MongoDB installation. > The source of the configuration error isn't clear, as neither the ISP nor Sanrio has answered questions on the matter. A MongoDB database open to the outside world on a public IP address?
Maybe someone was inspired by this article?
https://blog.shodan.io/its-still-the-data-stupid/
> At the moment, there are at least 35,000 publicly available, unauthenticated instances of MongoDB running on the Internet. [...] all of the exposed databases combined account for 684.8 TB of data.
Re: Database leak exposes 3.3M Hello Kitty fans
#19Earlier quoted context omitted.
These things happen to the best: In 2001, the World Economic Forum had their MS-SQLServer with personal data of the participants connected to the Internet. With the standard account enabled (user: "sa", password: empty). It then got "hacked" and the data leaked. German article about it: https://www.woz.ch/-41f8
Why is everybody immediately making these types of diversion responses regarding relational datastores to mongodb breaches? Mongo has popularity and 2 fixable issues that make the exposure numbers outweigh those of every other datastore right now. 1. There is no password prompt during installation. This was the same problem many relational databases had back in the day with default user credentials. Today, I don't kn…
MongoDB is repeating the same mistakes others made 15 years ago.
Re: Database leak exposes 3.3M Hello Kitty fans
#20Earlier quoted context omitted.
i.e. the default configuration But yeah, that's not good.
> i.e. the default configuration The default configuration for MongoDB is to listen on localhost only. Someone changed the configuration if it was listening on a public IP.
Feb 2015:
Discovered 40,000 vulnerable MongoDB databases on the Internet
http://securityaffairs.co/wordpress/33487/hacking/40000-vuln...
The changes were made after this, so we're only talking a few months now.