[SERVER-77334] LOGV2 messages may throw BSONObjectTooLarge exceptions Created: 19/May/23 Updated: 29/Oct/23 Resolved: 09/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Security
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 2023-06-12 | ||||
| Participants: | |||||
| Description |
|
It is possible for the log attributes when serialized using the custom serialize(), toBSON(), etc. members to trigger a BSONObjectTooLarge exception. Ideally the log line truncation performed by the logging subsystem would be performed at the same time to retain a portion of the log attributes rather than throwing an exception. Worth considering would be whether the logging subsystem should swallow other exceptions thrown by the custom serialization functions. |
| Comments |
| Comment by Githook User [ 07/Jun/23 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |