Add mongodb dbnames

[dabdine]

Adds the ability to retrieve database names & sizes from MongoDB.

How to Test

for MONGO_VERSION in "2.4" "2.6" "3.2" "3.6" "4.1" "4.2" "4.4" "5.0"; do { CID=$(docker run --rm --name test-mongo -d -p 1111:27017 mongo:$MONGO_VERSION) && sleep 1 && echo -n "127.0.0.1,," | ./zgrab2 mongodb -p 1111 | jq . && docker kill $CID; } done;

Notes & Caveats

Example output:

{
  "ip": "127.0.0.1",
  "data": {
    "mongodb": {
      "status": "success",
      "protocol": "mongodb",
      "result": {
        "is_master": {
          "is_master": true,
          "max_wire_version": 2,
          "max_bson_object_size": 16777216,
          "max_write_batch_size": 1000,
          "max_message_size_bytes": 48000000,
          "read_only": false
        },
        "build_info": {
          "version": "2.6.12",
          "git_version": "d73c92b1c85703828b55c2916a5dd4ad46535f6a",
          "sys_info": "Linux build5.ny.cbi.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49",
          "loader_flags": "-fPIC -pthread -Wl,-z,now -rdynamic",
          "compiler_flags": "-Wnon-virtual-dtor -Woverloaded-virtual -fPIC -fno-strict-aliasing -ggdb -pthread -Wall -Wsign-compare -Wno-unknown-pragmas -Winvalid-pch -pipe -Werror -O3 -Wno-unused-function -Wno-deprecated-declarations -fno-builtin-memcmp",
          "allocator": "tcmalloc",
          "bits": 64,
          "max_bson_object_size": 16777216,
          "javascript_engine": "V8",
          "build_environment": {}
        },
        "database_info": {
          "databases": [
            {
              "name": "local",
              "size_on_disk": 83886080,
              "empty": false
            },
            {
              "name": "admin",
              "size_on_disk": 1,
              "empty": true
            }
          ],
          "total_size": 83886080
        }
      },
      "timestamp": "2021-10-21T10:31:42-07:00"
    }
  }
}

[vl4deee11]

go naming way it use camelCase -> queryMsg

[dabdine]

The naming here follows the convention used elsewhere in the file. I can update those, but it may be best to instead separate coding standards compliance into a separate PR alongside some enforcement built within the git pipeline.

[vl4deee11]

Okay, I agree with you