[SERVER-31829] Limit number of document sequences in OP_MSG parser Created: 03/Nov/17 Updated: 30/Oct/23 Resolved: 10/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2017-11-13 |
| Participants: |
| Description |
|
The parser will reject as malformed any OP_MSG with more than 2 document sequences. This will be connection fatal. This is based on the fact that the current version should never have more than 1 in a valid request or 0 in a reply. This is not a format change and we may raise the limit in the future. |
| Comments |
| Comment by Githook User [ 07/Nov/17 ] |
|
Author: {'name': 'Mathias Stearn', 'username': 'RedBeard0531', 'email': 'mathias@10gen.com'}Message: |