We take all security bugs in systeminformation seriously. Thank you for improving the security of systeminformation. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
To ensure the timely response to your report, please ensure that the entirety of the report is contained, when reporting a security issue.
Report security bugs in third-party modules to the person or team maintaining the module.
Alpha and Beta releases are unstable and not suitable for production use. Vulnerabilities found in pre-releases should be reported according to the Reporting a Bug section. Due to the unstable nature of the branch it is not guaranteed that any fixes will be released in the next pre-release.
When we will receiving a security bug report, we will coordinate the fix and release process, involving the following steps:
- Confirm the problem and determine the affected versions.
- Audit code to find any potential similar problems.
- Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible to npm.
The functions inetChecksite(url) and inetLatency(host) perform network
requests to the target you pass in. They do not restrict the destination
to public hosts — internal or link-local addresses (e.g. http://127.0.0.1,
http://169.254.169.254/ cloud metadata endpoints) are reachable. Only the
file:, gopher:, telnet:, mailto:, news: and nntp: schemes are
blocked, and redirects are not followed.
If you call these functions with untrusted, user-supplied URLs or hosts in a server-side context, you are responsible for validating them first (e.g. denying private/loopback/link-local IP ranges). Never forward raw client input to these functions without such a check.
If you have suggestions on how this process could be improved please submit a pull request.