mongoaudit is a CLI tool for MongoDB auditing of servers, detecting poor security settings and performing automated penetration testing.
It is widely known that there are quite a few holes in MongoDB’s default configuration settings. This fact, combined with abundant lazy system administrators and developers, has led to what the press has called the MongoDB Ransack.
And just last week we wrote about Another MongoDB Hack Leaks Two Million Recordings Of Kids.
mongoaudit not only detects misconfigurations, known vulnerabilities and bugs but also gives you advice on how to fix them, recommends best practices and teaches you how to DevOp like a pro!
Features
mongoaudit tests that:
- MongoDB listens on a port different to default one
- Server only accepts connections from whitelisted hosts / networks
- MongoDB HTTP status interface is not accessible on port 28017
- MongoDB is not exposing its version number
- MongoDB version is newer than 2.4
- TLS/SSL encryption is enabled
- Authentication is enabled
- SCRAM-SHA-1 authentication method is enabled
- Server-side Javascript is forbidden
- Roles granted to the user only permit CRUD operations
- The user has permissions over a single database
Once you run any of the test suites provided by mongoaudit, it will offer you to receive a fully detailed report via email. This personalised report links to a series of useful guides on how to fix every specific issue and how to harden your MongoDB deployments.
You can download mongoaudit here:
Or read more here.
By default S3 buckets are not public.
They used to be IIRC, but I could be wrong, well I guess more accurately the easiest way to get access to it programmatically is just to set it to public.
Yes, it had to be configured to be open to the web. This story is not really about AWS. It’s about bad IT controls and careless engineering.
I wouldn’t even call this a hack, if it’s left open to the public.
Broadsoft was responsible for exposing the Time Warner Cable (TWC) data. Time Warner (TC) is an entirely separate entity (TC does NOT = TWC).
Hey thanks for that clarification Alan.
Also time Warner cable is no longer TWC . it is now spectrum.
Buckets have zero access beyond the creator. “Easiest way to grant access is to make it public”… that same statement applies to a cisco firewall in an onprem enterprise. And allow any rule is simple but terribly wrong. IAM or bucket policies are no more complex than any enterprise grade firewall. Lets not excuse the behavior of the admin due to ignorance.
Not excusing it, just saying it happens that way, same reason by MongoDB worked out of the box with no auth and listening on every interface. Not ideal, but a lot of things are done in the name of ease and speed of deployment rather than looking at it with an eye on risk and the repercussions.