You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization.
4
4
5
-
If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.**
5
+
If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.** If a potential security issue is inadvertently reported via a public issue or pull request, NVIDIA maintainers may limit public discussion and redirect the reporter to the appropriate private disclosure channels.
6
6
7
7
## Reporting Potential Security Vulnerability in an NVIDIA Product
8
8
@@ -11,11 +11,11 @@ To report a potential security vulnerability in any NVIDIA product:
11
11
- E-Mail: psirt@nvidia.com
12
12
- We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
13
13
- Please include the following information:
14
-
- Product/Driver name and version/branch that contains the vulnerability
15
-
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
16
-
- Instructions to reproduce the vulnerability
17
-
- Proof-of-concept or exploit code
18
-
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
14
+
- Product/Driver name and version/branch that contains the vulnerability
15
+
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
16
+
- Instructions to reproduce the vulnerability
17
+
- Proof-of-concept or exploit code
18
+
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
19
19
20
20
While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information.
0 commit comments