From a3acde8bfe63a1763b96c11806dcda24a5c273f0 Mon Sep 17 00:00:00 2001 From: Tony Murray Date: Tue, 7 Nov 2023 07:17:16 -0600 Subject: [PATCH] Use GitHub for vulnerability reporting (#15555) RIP huntr.dev --- SECURITY.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 5da19e3260..63fdff64f9 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -5,7 +5,7 @@ Only the most recent monthly release and daily release recieve security updates. LibreNMS is supported by volunteers, they all do their best to keep LibreNMS secure. -## Reporting a Vulnerability +## Finding a Vulnerability Like anyone, we appreciate the work people put in to find flaws in software and welcome anyone to do so with LibreNMS, this will lead to @@ -20,9 +20,8 @@ We are happy to attribute credit to the findings, but we ask that we're given a chance to patch any vulnerability before public disclosure so that our users can update as soon as a fix is available. - # Reporting a Vulnerability -If you discover a security vulnerability in librenms please disclose it via [our huntr page](https://huntr.dev/repos/librenms/librenms/). Bounty eligibility, CVE assignment, response times and past reports are all there. +If you discover a security vulnerability in librenms please disclose it via our [GitHub Security Advisories Page](https://github.com/librenms/librenms/security/advisories/new). -Thank you for improving the security of librenms. \ No newline at end of file +Thank you for improving the security of librenms.