From 40bf5f86da299c3a457d2594bf65ae720257d333 Mon Sep 17 00:00:00 2001 From: Jan Dvorak Date: Thu, 29 Apr 2021 13:24:18 +0200 Subject: [PATCH 1/3] Start work on security policy --- SECURITY.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000000..7b86670c5e --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,13 @@ +# Security Policy + +## Supported Versions + +| Version | Supported | +| ------- | ------------------ | +| 2.x.y | ✅ | +| 1.12.x | 🚧 | +| < 1.11.x | ❌ | + +## Reporting a Vulnerability + + From d91c87f50d5629ba92addc945539affc1d17dd8a Mon Sep 17 00:00:00 2001 From: Jan Dvorak Date: Thu, 6 May 2021 13:11:42 +0200 Subject: [PATCH 2/3] Adjust policy from Node.js --- SECURITY.md | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/SECURITY.md b/SECURITY.md index 7b86670c5e..2f26021cd7 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -10,4 +10,50 @@ ## Reporting a Vulnerability +Report security bugs to security@meteor.com. +Your report will be acknowledged within 24 hours, and you’ll receive a more +detailed response to your report within 48 hours indicating the next steps in +handling your submission. + +After the initial reply to your report, the security team will endeavor to keep +you informed of the progress being made towards a fix and full announcement, +and may ask for additional information or guidance surrounding the reported +issue. + +## Reporting a security bug in a third party module + +Security bugs in third party modules should be reported to their respective +maintainers. + +Thank you for improving the security of Meteor and its ecosystem. Your efforts +and responsible disclosure are greatly appreciated and will be acknowledged. + +## Disclosure policy + +Here is the security disclosure policy for Meteor + +* The security report is received and is assigned a primary handler. This + person will coordinate the fix and release process. The problem is confirmed + and a list of all affected versions is determined. Code is audited to find + any potential similar problems. Fixes are prepared for all releases which are + still under maintenance. These fixes are not committed to the public + repository but rather held locally pending the announcement. + +* A suggested embargo date for this vulnerability is chosen and a CVE (Common + Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability. + +* On the embargo date, the Node.js security mailing list is sent a copy of the + announcement. The changes are pushed to the public repository and new builds + are deployed to nodejs.org. Within 6 hours of the mailing list being + notified, a copy of the advisory will be published on the Node.js blog. + +* Typically the embargo date will be set 72 hours from the time the CVE is + issued. However, this may vary depending on the severity of the bug or + difficulty in applying a fix. + +* This process can take some time, especially when coordination is required + with maintainers of other projects. Every effort will be made to handle the + bug in as timely a manner as possible; however, it’s important that we follow + the release process above to ensure that the disclosure is handled in a + consistent manner. From bb1d5186fcdfb4f0596273ce25723c02bd32d235 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Filipe=20N=C3=A9vola?= Date: Wed, 12 May 2021 13:29:33 -0400 Subject: [PATCH 3/3] Update SECURITY.md --- SECURITY.md | 24 ++++-------------------- 1 file changed, 4 insertions(+), 20 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 2f26021cd7..3d8082de37 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -12,8 +12,8 @@ Report security bugs to security@meteor.com. -Your report will be acknowledged within 24 hours, and you’ll receive a more -detailed response to your report within 48 hours indicating the next steps in +Your report will be acknowledged within 2 work days, and you'll receive a more +detailed response to your report within 6 work days indicating the next steps in handling your submission. After the initial reply to your report, the security team will endeavor to keep @@ -21,6 +21,8 @@ you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue. +We don't have any bounty program. + ## Reporting a security bug in a third party module Security bugs in third party modules should be reported to their respective @@ -39,21 +41,3 @@ Here is the security disclosure policy for Meteor any potential similar problems. Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement. - -* A suggested embargo date for this vulnerability is chosen and a CVE (Common - Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability. - -* On the embargo date, the Node.js security mailing list is sent a copy of the - announcement. The changes are pushed to the public repository and new builds - are deployed to nodejs.org. Within 6 hours of the mailing list being - notified, a copy of the advisory will be published on the Node.js blog. - -* Typically the embargo date will be set 72 hours from the time the CVE is - issued. However, this may vary depending on the severity of the bug or - difficulty in applying a fix. - -* This process can take some time, especially when coordination is required - with maintainers of other projects. Every effort will be made to handle the - bug in as timely a manner as possible; however, it’s important that we follow - the release process above to ensure that the disclosure is handled in a - consistent manner.