Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30361

mongod.conf bindIp option accept bogus parameters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.18, 3.4.10, 3.5.11
    • Component/s: Admin
    • Labels:
      None
    • Environment:
      3.4.6 community
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2, v3.0
    • Steps To Reproduce:
      Hide

      Using 3.4.6.
      1. Get a fresh copy of mongod.conf
      2. Change values as needed.
      3. set the bindIp option value to something like " bindIp: [somestuff] "
      4. start mongod using that file (mongod.conf)
      5. use " netstat -tanp | grep LISTEN " to verify THAT mongod is listening on 0.0.0.0:portnumber

      Show
      Using 3.4.6. 1. Get a fresh copy of mongod.conf 2. Change values as needed. 3. set the bindIp option value to something like " bindIp: [somestuff] " 4. start mongod using that file (mongod.conf) 5. use " netstat -tanp | grep LISTEN " to verify THAT mongod is listening on 0.0.0.0:portnumber
    • Sprint:
      Platforms 2017-08-21

      Description

      bindIp accepts ANY bogus string as a parameter if it is enclosed in square brackets.

      I found out a mongo.conf that had a list of values (IP's) enclosed in square brackets []. However mongod was listening on 0.0.0.0:portnumber.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: