As a project under the collective GitHub organization as well as a dependency of Plone, icalendar follows the security policy of Plone.

• Report a security issue.
• Security announcements
• Read more about security in Plone.

Security vulnerabilities are fixed only for the latest version of icalendar.

The maintainers of icalendar will coordinate with the Plone security team.

If we determine that your report may be a security issue with the project, we may contact you for further information. We volunteers ask that you delay public disclosure of your report for at least ninety (90) days from the date you report it to us. This will allow sufficient time for us to process your report and coordinate disclosure with you.

Once verified and fixed, the following steps will be taken:

• We will use GitHub's Security Advisory tool to report the issue.

• GitHub will review our Security Advisory report for compliance with Common Vulnerabilities and Exposures (CVE) rules. If it is compliant, they will submit it to the MITRE Corporation to generate a CVE. This in turn submits the CVE to the National Vulnerability Database (NVD). GitHub notifies us of their decision.

• Assuming it is compliant, we then publish our Security Advisory on GitHub, which triggers the next steps.

• GitHub will publish the CVE to the CVE List.

• GitHub will broadcast our Security Advisory via the GitHub Advisory Database.

• GitHub will send security alerts to all repositories that use our package (and have opted into security alerts). This includes Dependabot alerts.

• We will make a bug-fix release.

• We will send an announcement through our usual channels:

  • the change log
  • the GitHub releases of icalendar
  • Plone's Security Announcements

• We will provide credit to the reporter or researcher in the vulnerability notice.