Check for corrupted OP_REPLY message header

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.0
    • Affects Version/s: None
    • Component/s: Connection Management
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When reading a message from the server, check for various ways the OP_REPLY message header may be corrupted and throw MongoInternalException if any are found:

      • message length < reply header length
      • message length > max message length
      • num documents returned < 0
      • message length - reply header length < num documents returned * minimum BSON document length

            Assignee:
            Jeffrey Yemin
            Reporter:
            Rathi Gnanasekaran (Inactive)
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: