[SERVER-67877] Check BSON UUID type in validate command Created: 07/Jul/22 Updated: 29/Oct/23 Resolved: 02/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Richard Hausman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-07-25, Execution Team 2022-08-08 |
| Participants: |
| Description |
|
Currently when we validate BSON Binary data type, we simply skip over it without further checking if the content comply to the specification. Valid UUIDs are 16-byte long but in BSON documents they can be arbitrary lengths and we do not check it. We need to make the validate command to catch this inconsistency while not for regular writes. We can already create BSON documents with an invalid UUID in the shell by
We should also add unit tests for this. |
| Comments |
| Comment by Richard Hausman (Inactive) [ 02/Aug/22 ] |