File tree Expand file tree Collapse file tree 1 file changed +17
-0
lines changed Expand file tree Collapse file tree 1 file changed +17
-0
lines changed Original file line number Diff line number Diff line change 49
49
- [ Type casting] ( #type-casting )
50
50
- [ Connection Flags] ( #connection-flags )
51
51
- [ Debugging and reporting problems] ( #debugging-and-reporting-problems )
52
+ - [ Security issues] ( #security-issues )
52
53
- [ Contributing] ( #contributing )
53
54
- [ Running tests] ( #running-tests )
54
55
- [ Todo] ( #todo )
@@ -1410,6 +1411,22 @@ will have:
1410
1411
* As much debugging output and information about your environment (mysql
1411
1412
version, node version, os, etc.) as you can gather.
1412
1413
1414
+ ## Security issues
1415
+
1416
+ Security issues should not be first reported through GitHub or another public
1417
+ forum, but kept private in order for the collaborators to assess the report
1418
+ and either (a) devise a fix and plan a release date or (b) assert that is not
1419
+ not a security issues (in which case it can be posted in a public forum, like
1420
+ a GitHub issue).
1421
+
1422
+ The primary private forum is email, either by emailing the module's author or
1423
+ opening a GitHub issue simply asking to whom a security issues should be
1424
+ addresses to without disclosing the issue or type of issue.
1425
+
1426
+ An ideal report would include a clear indication of what the security issue is
1427
+ and how it would be exploited, ideally with an accompaning proof of concept
1428
+ ("PoC") for collaborators to work again and validate potentional fixes against.
1429
+
1413
1430
## Contributing
1414
1431
1415
1432
This project welcomes contributions from the community. Contributions are
You can’t perform that action at this time.
0 commit comments