-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
Use Case
As a user of mongodb node team driver repos
I want to ensure that potentially-sensitive user-supplied values arent revealed in errors or logs
So that sensitive information disclosure does not take place
User Experience
- User supplied values should not be present in error messages as they could contain sensitive values
Dependencies
- N/A
Risks/Unknowns
- Should we only scope-in values which we think can contain user-supplied values, or omit them completely from errors?
- Some upstream calls which yield errors with user-supplied values in them could be relied on by users, causing a breaking change to be introduced.
Acceptance Criteria
Implementation Requirements
- All repo's which surface user input into logs/errors should redact the user input (e.g: an invalid connstr should not be embedded in an error, potentially revealing the password supplied) (use a subtask per repo)
Testing Requirements
- unit test, spec test sync, etc
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- N/A
See: https://jira.mongodb.org/browse/ENGSEC-675 for more information