Note that in the case of MongoDB, the lack of authorization at the shell is by design. It is possible to connect unauthenticated to any MongoDB shell. However you are limited to just seeing the version number of mongo and whether the node you are connected to is a primary or secondary. Unless you authenticate as a user account with privileges for a given database, you cannot make any queries or perform any operations. Access to a mongo shell is not sufficient evidence that the database is "misconfigured."
Of course, one can argue whether this is a design flaw of MongoDB, and can certainly argue that all Mongo instances should whitelist IP addresses that connect to them, regardless of the level of authentication necessary to perform operations on a given instance.